Re: Re: SQL Integration

----- Original Message ----- 
From: "Doug H" <doug00-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx>
To: <dev-lK5OYVT/OUeB6hVKlEQLGA@xxxxxxxxxxxxxxxx>
Sent: Tuesday, February 22, 2005 9:20 PM
Subject: Re: [boo-dev] Re: SQL Integration


> On Fri, 18 Feb 2005 18:39:54 +0100, Hans-Christian Holm
> <hchrholm-f/vm7P8qpiNhl2p70BpVqQ@xxxxxxxxxxxxxxxx> wrote:
> > Perhaps this wish should be expressed in a more general way: Could it be 
> > or
> > is it possible to extend and customise Boo beyond macros, like defining 
> > new
> > tokens, new syntax rules, custom IL generation etc? I'd like to see not 
> > only
> > embedded SQL and XML processing like in Comega, but even embedded IL 
> > (like
> > embedded assembly code in some languages). Could Boo eventually become 
> > some
> > kind of a meta-language, a base for special needs so that you don't have 
> > to
> > design a language and a compiler from scratch everytime you'd like a 
> > domain
> > specific language?
>
> I think especially with the next all-boo version of the compiler,
> plugging in optional services like this will be even easier.
> See Rodrigo's notes on compiler profiles:
> http://blogs.codehaus.org/people/bamboo/archives/000919_compiler_pipelines_and_compiler_profiles.html
> See also http://jira.codehaus.org/browse/BOO-82

One approach to this could to preprocess source files for stuff that doesn't 
suit the Boo parser. Not half as elegant, though. However, I've looked 
through the compiler source code, and so far, I haven't found any place to 
plug in a preprocessor. As soon as booc.exe has added a FileInput object to 
the BooCompiler.Input, everything is read only as far as source code is 
concerned. While it's trivial do read and preprocess files before adding 
them to a BooCompiler, it would be nice to have a more general way to add 
preprocessing so that you still can use booc.exe. Or did I miss something 
here?

Hans-Christian