Alan Manuel Gloria:
> So... no more unread-char?  Do I remove the unread-char impl as well
> as the 2nd char buffer on R5RS compatibility layer?

Yes, please do.  That would simplify things, and it was the reason we switched 
to "!" as the non-whitespace indent character.

On a related note:  I started to implement a # readtable.  I used a 
guile-inspired interface:
(readable-read-hash-extend chr proc).  HOWEVER, the "proc" routine needs access 
to the my-read-char.  I hate to export that as well, though we can if we must.  
Is there another way to do what's needed, now that we don't need unread-char?

--- David A. Wheeler

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 
Readable-discuss mailing list

Reply via email to