On Fri, Jul 20, 2012 at 8:40 PM, David A. Wheeler <dwhee...@dwheeler.com> wrote:
> I kept the "sugar" system separate because I thought we were just going to 
> use SRFI-49 as-is, possibly with some bug fixes.  Obviously that is NOT the 
> case.  While we *could* keep the "sweet" system separate and able to build on 
> other things, I think it's not worth it.  We already have a case 
> (period-space indents) where it would be *useful* to have a special interface 
> between the indentation processor and underlying modern-expression reader.  
> So I think we shouldn't expose a separate indentation processor like "sugar".

Ah, I see.  My main concern was that the current module structure has
sugar separately loadable from modern, so I thought you wanted to
retain that, but use a more Scheme-y interface.  So if you prefer to
have complete integration of modern into sugar, that's fine.  You lose
the ability to get just sugar without modern, but who'd want that? ^^;

> I think we do NOT want a lot of modules, in fact, ideally we only want one.
>
> Modules are notoriously painful to port, they're not the same between Schemes 
> (unless they implement R6RS modules).  And we don't really need multiple 
> modules; the names can easily include prefixes to determine which is which, 
> and there's some interconnection between them anyway.

Actually, the main purpose of that is to support the current usage of
(use-modules (sugar)).  Currently, this importation auto-enables the
syntax at the REPL and all future use-modules.  So the modules are
just convenience modules, possibly for interactive usage, where you
just suddenly load (use-modules (sweet)) and then switch to using
sweet-expressions.

Basically, instead of doing (use-modules (readable sweet-impl))
(replace-read modern-read) you just type in (use-modules (readable
modern)).  Otherwise, it's just a convenience module that does not
need to be ported at all, and even if ported is just composed of the
single expression (replace-read modern-read) or (replace-read
sweet-read), which I think is ridiculously trivial to port.

Sincerely,
AmkG

------------------------------------------------------------------------------
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