http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660@Luke You may get decent error messages, but debugging's a pain. Compiler treates a bunch of fluent interface calls as one line of code, so it becomes difficult to step in to individual calls. ScottGu suggested debugger visualizers at altnetconf, but they don't work for a lot of fluent interface scenarios. I haven't really found a better solution... http://ayende.com/3006/a-time-for-a-dsl#comment3http://ayende.com/3006/a-time-for-a-dsl#comment3Tue, 04 Dec 2007 20:20:25 GMTThat depends on the type and complexity of the DSL. The parser errors are not really great, but anything else is under you control. http://ayende.com/3006/a-time-for-a-dsl#comment2http://ayende.com/3006/a-time-for-a-dsl#comment2Tue, 04 Dec 2007 16:19:58 GMTWhat has your experience been with error messages in the DSLs you've created? In my experience, MS's C# compiler gives excellent error messages, at least until you get into serious extension method/type inference/lambda territory. When a your DSLs get a bit on the complex side, do the error messages suffer? http://ayende.com/3006/a-time-for-a-dsl#comment1http://ayende.com/3006/a-time-for-a-dsl#comment1Tue, 04 Dec 2007 13:38:37 GMT