Re: .NET Compiler for Interactive Fiction

Neelakantan Krishnaswami <neelk@alum.mit.edu>
14 Mar 2003 11:03:10 -0500

          From comp.compilers

Related articles
.NET Compiler for Interactive Fiction david.cornelson@iflibrary.com (David A. Cornelson) (2003-02-21)
Re: .NET Compiler for Interactive Fiction marcov@toad.stack.nl (Marco van de Voort) (2003-02-24)
Re: .NET Compiler for Interactive Fiction neelk@alum.mit.edu (Neelakantan Krishnaswami) (2003-02-24)
Re: .NET Compiler for Interactive Fiction david.cornelson@iflibrary.com (David A. Cornelson) (2003-03-09)
Re: .NET Compiler for Interactive Fiction tbandrow@unitedsoftworks.com (2003-03-09)
Re: .NET Compiler for Interactive Fiction neelk@alum.mit.edu (Neelakantan Krishnaswami) (2003-03-14)
Re: .NET Compiler for Interactive Fiction lars@bearnip.com (2003-03-14)
Re: .NET Compiler for Interactive Fiction david.cornelson@iflibrary.com (David A. Cornelson) (2003-03-14)
Re: .NET Compiler for Interactive Fiction marcov@toad.stack.nl (Marco van de Voort) (2003-03-14)
Re: .NET Compiler for Interactive Fiction tbandrow@unitedsoftworks.com (2003-03-16)
Re: .NET Compiler for Interactive Fiction tbandrow@unitedsoftworks.com (2003-03-16)
Re: .NET Compiler for Interactive Fiction lex@cc.gatech.edu (Lex Spoon) (2003-03-17)
[3 later articles]
| List of all articles for this month |

From: Neelakantan Krishnaswami <neelk@alum.mit.edu>
Newsgroups: comp.compilers
Date: 14 Mar 2003 11:03:10 -0500
Organization: AT&T Broadband
References: 03-02-125 03-02-147 03-03-043
Keywords: design
Posted-Date: 14 Mar 2003 11:03:10 EST

tj bandrowsky <tbandrow@unitedsoftworks.com> wrote:
>
> > It sounds like what you want is a macro system, that takes a domain-
> > specific syntax and expands it into C# code.
>
> See I don't know that he wants a code expander and the idea of
> writing his own compiler to the CLR is rather intriguing. If
> anything, his DSL would not be limited in a lot of ways because he
> could easily expose the entire .NET framework to developers using
> his DSL.


That's not quite what I'm suggesting. I am suggesting writing a macro
package that embeds a domain-specific sublanguage into C#. Then you
don't need to do any work exposing the .NET framework to the user,
because you can always fall back to C# if the DSL doesn't cover the
case you want.


--
Neel Krishnaswami
neelk@alum.mit.edu


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.