Heya, it seems *> is going to be a bit of a bother...

It's fine to detect <* in readblock-internal, then eat up horiz
whitespace and then call as a subroutine the upper-level
sugar-start-expr repeatedly until we somehow get to a *>.

However, when readblock-internal detects *> while reading a head, it
needs to somehow signal the next higher readblock-internal in the call
chain and return to that (since *> is two characters, we can't unread
them both).

Hmmmmm.....

Any ideas?  I have an idea, but I feel it's kinda ugly, so I'll
solicit some more ideas here before I show my own ^^

---

Oh and yeah, I decided to change how rulesets are handled in my game.
Instead of using Guile modules, I read in the ruleset as a datum and
create a table (an immutable association table) from the ruleset
datum.  The datum processor can also process a special "include"
directive embedded in the datum, so I can do something like:

; toplevel stdp4.rule
unit-types
! include stdp4/unit-types.rule
toplevel-rule-declaration
...

; stdp4/unit-types.rule
<BasicInfantry>
! name "Basic Infantry"
! help "Basic Infantry defeats everyone, except for all the more
advanced units, of which there are many."
! unit-power 20
! unit-type-characteristics
! ...

<ScoutDrone>
! name "Scout Drone"
! help "Scout Drones drone around scouting."
! unit-power 15
! unit-type-characteristics
! ...

unit-type-declaration
...

Probably quite a bit less flexible though.

So... I don't really need the "indent everything" symbol anymore.  Of
course, R6RS library needs it, and probably single-variable let needs
it too.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Readable-discuss mailing list
Readable-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/readable-discuss

Reply via email to