http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Craig, that is a _good_ reason :-) http://ayende.com/2856/multi-file-dsls#comment4http://ayende.com/2856/multi-file-dsls#comment4Fri, 12 Oct 2007 13:29:09 GMTLoL If I can learn your secret to time management, I might be able to squeeze in some blogging. I have 3 kids under the age of 4, and you would be surprised at the lengths I go to just to get keep my OSS effots going ;^) http://ayende.com/2856/multi-file-dsls#comment3http://ayende.com/2856/multi-file-dsls#comment3Fri, 12 Oct 2007 12:39:22 GMTAndy, actually, all you need is a booc -p:CustomerStep But when we are talking about DSLs, we are already talking about setting up the compiler yourself. Brail, BooBS, Rhino ETL, Binsor, etc - all do it this way http://ayende.com/2856/multi-file-dsls#comment2http://ayende.com/2856/multi-file-dsls#comment2Thu, 11 Oct 2007 13:08:49 GMTNew to Boo (and am loving it) but... Doesn't doing it this way mean that you need to setup the compiler or interpreter yourself? ie you can't use booc, booi or booish as standard. booish has a "load" verb which includes an external file. It would seem possible that you should be able to create a macro to achieve the same effect. I've come close (basically a rewrite of your compiler step as a macro. Can't quite get it to work (as it's pretty much the first thing I've done with Boo). I think the failing with the way I'm doing it is that it won't be compiled as an assembly reference (as your would) but would be loaded dynamically. Probably fine for most purposes though. Thoughts? http://ayende.com/2856/multi-file-dsls#comment1http://ayende.com/2856/multi-file-dsls#comment1Thu, 11 Oct 2007 11:07:12 GMT