<feed xmlns='http://www.w3.org/2005/Atom'>
<title>zigling-exercises.git/src/ipc.zig, branch main</title>
<subtitle>My copy of the Zigling exercises and their solutions. See the original at https://codeberg.org/ziglings/exercises
</subtitle>
<id>https://git.muftee.net/zigling-exercises.git/atom?h=main</id>
<link rel='self' href='https://git.muftee.net/zigling-exercises.git/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.muftee.net/zigling-exercises.git/'/>
<updated>2023-05-19T17:27:33Z</updated>
<entry>
<title>build: remove `ZiglingStep.eval`</title>
<updated>2023-05-19T17:27:33Z</updated>
<author>
<name>Manlio Perillo</name>
<email>manlio.perillo@gmail.com</email>
</author>
<published>2023-05-19T13:28:20Z</published>
<link rel='alternate' type='text/html' href='https://git.muftee.net/zigling-exercises.git/commit/?id=699f877bd51bc93717c76573a61a7b5598f1bd82'/>
<id>urn:sha1:699f877bd51bc93717c76573a61a7b5598f1bd82</id>
<content type='text'>
Remove the `ZiglingStep.eval` method and the src/ipc.zig source code.
Use `Step.evalZigProcess`, instead. This greatly simplifies the code.

Print the error messages and error bundle in `ZiglingStep.make`, both in
case of error and success.

Additionally, remove the `ZiglingStep.is_testing` field, since it is no
longer necessary.
</content>
</entry>
<entry>
<title>build: restore compatibility support again</title>
<updated>2023-04-18T10:22:30Z</updated>
<author>
<name>Manlio Perillo</name>
<email>manlio.perillo@gmail.com</email>
</author>
<published>2023-04-18T10:22:30Z</published>
<link rel='alternate' type='text/html' href='https://git.muftee.net/zigling-exercises.git/commit/?id=b39c7e61ef3d0b2ac28a2ce70ef549f2fac834b1'/>
<id>urn:sha1:b39c7e61ef3d0b2ac28a2ce70ef549f2fac834b1</id>
<content type='text'>
Commit e214c44 (build: update ZiglingStep to the new API) broke again
the compatibility support for old compilers, due to the use of the
multi-object for loop syntax.

Move the Zig IPC support code to src/ipc.zig.

Use the while statement, instead of the for statement.
</content>
</entry>
</feed>
