<feed xmlns='http://www.w3.org/2005/Atom'>
<title>chromatopelma/csc/loop-test.csc, branch main</title>
<subtitle>Partial r7rs implementation with a focus on ease of implementation and a reusable library. Work in progress.</subtitle>
<id>https://code.roseh.moe/chromatopelma/atom/csc/loop-test.csc?h=main</id>
<link rel='self' href='https://code.roseh.moe/chromatopelma/atom/csc/loop-test.csc?h=main'/>
<link rel='alternate' type='text/html' href='https://code.roseh.moe/chromatopelma/'/>
<updated>2022-08-02T02:35:19Z</updated>
<entry>
<title>Modify the project structure.</title>
<updated>2022-08-02T02:35:19Z</updated>
<author>
<name>Rose Hogenson</name>
<email>rhogenson@posteo.net</email>
</author>
<published>2022-08-02T02:35:19Z</published>
<link rel='alternate' type='text/html' href='https://code.roseh.moe/chromatopelma/commit/?id=acc561366f3fe6ec0377103f52ef0f7e923711c9'/>
<id>urn:sha1:acc561366f3fe6ec0377103f52ef0f7e923711c9</id>
<content type='text'>
Now the lib directory contains what will eventually end up on the
user's /usr/lib/csc. When I write make install, it will copy all of
the .csc files from lib into the destination lib directory. This means I
can start working on the standard library in lib/scheme.
</content>
</entry>
<entry>
<title>Fix a potential R7RS issue.</title>
<updated>2022-07-27T02:24:10Z</updated>
<author>
<name>Rose Hogenson</name>
<email>rhogenson@posteo.net</email>
</author>
<published>2022-07-27T02:24:10Z</published>
<link rel='alternate' type='text/html' href='https://code.roseh.moe/chromatopelma/commit/?id=becfaeb778a3c8ba241e2155b998d6b27dcfad0c'/>
<id>urn:sha1:becfaeb778a3c8ba241e2155b998d6b27dcfad0c</id>
<content type='text'>
I was using the load procedure to load a program, but by a strict
reading of R7RS, load can only handle expressions and definitions, not
imports. So instead I'm defining each test as a library, and using the
environment procedure to load them at runtime.
</content>
</entry>
<entry>
<title>Fix a bug in loop with nested collect statements.</title>
<updated>2022-07-25T02:07:17Z</updated>
<author>
<name>Rose Hogenson</name>
<email>rhogenson@posteo.net</email>
</author>
<published>2022-07-25T02:07:17Z</published>
<link rel='alternate' type='text/html' href='https://code.roseh.moe/chromatopelma/commit/?id=192ab9c4e21bab8c08a640b349fa9630a9a672df'/>
<id>urn:sha1:192ab9c4e21bab8c08a640b349fa9630a9a672df</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Improve the loop macro collect statement.</title>
<updated>2022-07-24T19:52:21Z</updated>
<author>
<name>Rose Hogenson</name>
<email>rhogenson@posteo.net</email>
</author>
<published>2022-07-24T19:52:21Z</published>
<link rel='alternate' type='text/html' href='https://code.roseh.moe/chromatopelma/commit/?id=c6b74224fe669bc9d180a409ad13ed269631b316'/>
<id>urn:sha1:c6b74224fe669bc9d180a409ad13ed269631b316</id>
<content type='text'>
Now you can use multiple collect statements and they will all accumulate
into the same variable. I think in common lisp you could collect into
the same variable even with collect x into, but it's pretty unclear to
me how to do that in Scheme. How would we know that they are the
same variable?
</content>
</entry>
<entry>
<title>Fix the bugs in loop.</title>
<updated>2022-01-25T16:42:20Z</updated>
<author>
<name>Rose Hogenson</name>
<email>rhogenson@posteo.net</email>
</author>
<published>2022-01-25T16:42:20Z</published>
<link rel='alternate' type='text/html' href='https://code.roseh.moe/chromatopelma/commit/?id=384688fa95abaf0fcbeb1c187b1574ebd6cec456'/>
<id>urn:sha1:384688fa95abaf0fcbeb1c187b1574ebd6cec456</id>
<content type='text'>
It works! Sometimes it emits nested loops!
</content>
</entry>
<entry>
<title>Add a loop macro.</title>
<updated>2022-01-23T01:51:20Z</updated>
<author>
<name>Rose Hogenson</name>
<email>rhogenson@posteo.net</email>
</author>
<published>2022-01-23T01:51:20Z</published>
<link rel='alternate' type='text/html' href='https://code.roseh.moe/chromatopelma/commit/?id=a54f483b1f9ae3f03f1f00124eec296c2d9218d7'/>
<id>urn:sha1:a54f483b1f9ae3f03f1f00124eec296c2d9218d7</id>
<content type='text'>
</content>
</entry>
</feed>
