Funny, I've just learned Boo and one of my first thoughts were "this
is
really interesting, with all that flexibility and extensibility in
the
compiler pipeline, perhaps it's even possible to embed SQL, like
in
Comega?"...
Boo isn't lacking database support more than any other CLR language
I've
seen (except for Comega), it's all there in the ADO.NET class library.
But
then, no matter how well the ADO.NET classes work, I'm still fed up with
all
that trivial data layer work (even with the great improvements in DataSet
in
2.0 or when using ORMs like nHibernate), and would like to see
something
more streamlined and elegant.
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?
These are just some random thoughts on a friday afternoon, I don't
even
know if they belong in this newsgroup...
Hans-Christian
(This is my fourth attempt to post to this
list. First I posted to nntp/gmane with Outlook Express and a "nospam" "From"
address, nothing happened. Then I realised gmane needed a valid address for
verification, but still nothing. The I read the gmane FAQ twice and used the
gmane web form, but nothing. This time I used dev-subcribe-lK5OYVT/OUfxTkFNYy7Diw@xxxxxxxxxxxxxxxxxx etc.,
hope it works now.)
