> when will this be???
> What about to tell us some features :-))

2.00 works off of config files.  (There's a default one, or you can put a
#use line in your bake file, or you can specify it on the command line.)

Anyway, the config files allow it to use more than one compiler.  I've got
config files for emx and CSET++.  I should probably do them for watcom and
borland too, but don't have those compilers.

The config files also allow support for new file types (such as som's .idl
files), and the extension hack I had in 1.00 (file.emx for an emulated unix
.exe file) is now taken care of in the config files (different config file
for emx producing 32 bit native OS/2 files, and emx producing emulated unix
files.)

In theory, with the config files you could make bake work with pascal or
basic or something...  If you wanted to work out your own config file.  You
could even make it the default (just replace bake.cfg with a different
config file.)

That's what I was thinking of, anyway.  I was unaware that anyone was
actually USING bake.  (I haven't had much time to work on my own projects
since coming to IBM, and at IBM we use VisualAge and CSET.  (I worked out
the config file idea to make bake work with cset and use SOM, because I
really really HATE make files.  Whole reason I did it in the first place,
and for compiling our project on the power PC with the metaware compiler,
we had the mother of all make files...  Seriously nasty.)

Rob
 
--- Xblat