Related articles |
---|
Designing a Domain-specific language dror.openu@gmail.com (2017-05-23) |
Re: Designing a Domain-specific language bc@freeuk.com (bartc) (2017-05-23) |
Re: Designing a Domain-specific language DrDiettrich1@netscape.net (Hans-Peter Diettrich) (2017-05-24) |
Re: Designing a Domain-specific language laguest9000@googlemail.com (lucretia9@lycos.co.uk) (2017-05-24) |
Re: Designing a Domain-specific language dror.openu@gmail.com (2017-05-25) |
Re: Designing a Domain-specific language bc@freeuk.com (bartc) (2017-05-27) |
From: | "lucretia9@lycos.co.uk" <laguest9000@googlemail.com> |
Newsgroups: | comp.compilers |
Date: | Wed, 24 May 2017 04:13:19 -0700 (PDT) |
Organization: | Compilers Central |
References: | 17-05-007 |
Injection-Info: | miucha.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="63248"; mail-complaints-to="abuse@iecc.com" |
Keywords: | design |
Posted-Date: | 25 May 2017 10:58:56 EDT |
Don't do what C and C++ do and implement includes, it's a severely brain dead
approach. Implement a real module / unit / package system and when the
compiler reaches and import / use / with / whatever statement, the compiler
needs to read in the symbol table for that.
Do what Ada does and allow the driver to take many files and just compile
them.
Luke.
Return to the
comp.compilers page.
Search the
comp.compilers archives again.