This is the mail archive of the guile@sourceware.cygnus.com mailing list for the Guile project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: A module system should resolve, not introduce, name conflicts


Jost Boekemeier <jostobfe@calvados.zrz.TU-Berlin.DE> writes:

> > > Guile can't use such a meta-language because every module
> > > may have its own repl.  A module written in tcl for example
> > > may have a tcl repl, a module written in perl may have
> > > a perl repl etc.
> > 
> > This is exactly why the meta-language should be associated with the
> > repl instead of being implemented by bindings imported by individual
> > modules.  There is no reason why the Guile Scheme repl can't use the
> > meta-language in Scheme48.
> 
> How that?  The package (lang tcl) may contribute its own repl
> which interprets tcl syntax, the perl package may contribute
> its own repl which interprets perl syntax.  Isn't ",in"
> a valid perl construct?  

Again: The meta-language is not some global thing but associated with
the repl.  This means that there is one syntax for the Scheme repl,
and other for other repls.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]