<feed xmlns='http://www.w3.org/2005/Atom'>
<title>cie-pseudocode-compiler.git/include/cps/Diagnostics.h, branch main</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>https://git.ov4.org/cie-pseudocode-compiler.git/atom/include/cps/Diagnostics.h?h=main</id>
<link rel='self' href='https://git.ov4.org/cie-pseudocode-compiler.git/atom/include/cps/Diagnostics.h?h=main'/>
<link rel='alternate' type='text/html' href='https://git.ov4.org/cie-pseudocode-compiler.git/'/>
<updated>2026-10-22T15:33:15Z</updated>
<entry>
<title>fix(diagnostics): print each identical diagnostic once</title>
<updated>2026-10-22T15:33:15Z</updated>
<author>
<name>_ov4</name>
<email>ov4@ov4.org</email>
</author>
<published>2026-10-22T15:33:02Z</published>
<link rel='alternate' type='text/html' href='https://git.ov4.org/cie-pseudocode-compiler.git/commit/?id=5e84edbe1a79c6a7752ee276ea6c1a4daef4fa8e'/>
<id>urn:sha1:5e84edbe1a79c6a7752ee276ea6c1a4daef4fa8e</id>
<content type='text'>
Co-Authored-By: Claude Sonnet 5.5 &lt;noreply@anthropic.com&gt;
</content>
</entry>
<entry>
<title>feat(driver): color diagnostics like gcc with -fdiagnostics-color</title>
<updated>2026-10-21T14:06:54Z</updated>
<author>
<name>_ov4</name>
<email>ov4@ov4.org</email>
</author>
<published>2026-10-21T14:06:54Z</published>
<link rel='alternate' type='text/html' href='https://git.ov4.org/cie-pseudocode-compiler.git/commit/?id=899c2af576124df2918fd2ae976434df0ebbae5b'/>
<id>urn:sha1:899c2af576124df2918fd2ae976434df0ebbae5b</id>
<content type='text'>
Add -fdiagnostics-color[=auto|always|never] and -fno-diagnostics-color.
The default auto mode colors only a terminal stderr (TERM set and not
dumb on Unix; a console that accepts VT sequences on Windows), so test
harnesses, the desktop bundle and other pipes stay plain.

Every diagnostic label now comes from cps::diagnosticPrefix, which emits
gcc's default GCC_COLORS bytes: bold locus, bold red error/fatal error,
bold magenta warning, bold cyan note. compilation terminated., runtime
messages of the compiled program and lld output are unchanged.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
</content>
</entry>
<entry>
<title>feat(diagnostics): print source diagnostics in gcc file:line: layout</title>
<updated>2026-10-21T14:03:31Z</updated>
<author>
<name>_ov4</name>
<email>ov4@ov4.org</email>
</author>
<published>2026-10-21T14:03:31Z</published>
<link rel='alternate' type='text/html' href='https://git.ov4.org/cie-pseudocode-compiler.git/commit/?id=b4ffb2d9498560557821714e2d4651279dd6817c'/>
<id>urn:sha1:b4ffb2d9498560557821714e2d4651279dd6817c</id>
<content type='text'>
Lexer, parser, driver and codegen diagnostics now read
"&lt;path&gt;:&lt;line&gt;: error: &lt;message&gt;" instead of "error: &lt;message&gt; at line N
in &lt;path&gt;". The path is always printed as given on the command line.
Call sites pass the bare message to cps::sourceError/sourceWarning, which
carry printf format checking; reportError routes through the same helper.

The suite iii harness parses the new layout and matches the reason
against the message only. iii/template-class-pack-field passed only
because its reason regex matched the case path, so it is now
case-insensitive.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
</content>
</entry>
<entry>
<title>refactor(diag): file-qualified diagnostic locations</title>
<updated>2026-10-17T09:09:03Z</updated>
<author>
<name>_ov4</name>
<email>ov4@ov4.org</email>
</author>
<published>2026-10-17T09:09:03Z</published>
<link rel='alternate' type='text/html' href='https://git.ov4.org/cie-pseudocode-compiler.git/commit/?id=dc645a36aaade7087ade574cefe69ce7bb29753e'/>
<id>urn:sha1:dc645a36aaade7087ade574cefe69ce7bb29753e</id>
<content type='text'>
Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
</content>
</entry>
</feed>
