Re: A "Via Pascal" Modula 2 Compiler ?

Marco van de Voort wrote:
> On 2007-01-15, JP2R <jp-dezaire@[EMAIL PROTECTED]
> wrote:
>
> If you can really separate them that way. FPC had to compete with BP
from
> the beginning, and thus adopted a "production" mentality early on. And
that
> meant often: seemless integration.

Yes, and a lot more work to understand and reuse

> > The main problems are : ..... which is hard to accept by both
communities ...
>
> Better than doing the same with C, which is the other choice.
 I think so, and thanks for this sentence :+)

> I also think the integrated way would be the best. IOW parameterise
scanner
> and parser so they can parse both. This because the scanner and parser
> already have flexibility because of the various pascal dialects.
>
I don't think it will be sufficient  -  and in the best case I'll not
get something better than I already have . I told of the problem of
Procs assignements - how can you do it properly without a minimalist
semantic ?
- in FPC dialect  ....MyProc :=  @[EMAIL PROTECTED]
 in BP dialect  ....  MyProc := ProcSomething   (as in M2)
if you don't know that ProcSomething is a Proc  and not  a Var (not
speaking about the corectness of assignement)

Even in src2src translating  you need something more than simply
scanning and parsing if you want to do things right
An other example :
CONST  Wrt  := InOut. Write  ....   wich is in reality a  #define  Wrt
Inout.Write ...   if you rewrite 'word for word' you'll have an error
in pascal , so at the very least you have to preprocess (I have place
holders for that, but right now I don't catch this ), some look-up
tables etc.  wich I already have in order to avoid clashes between
idents and reserved words of Pascal, and idents of different cases
(upper/lower/mixed..)  so  the  growing of the project will not be so
im****tant.
So I think the options are
-src2src
- branch after a preprocess, just a bit more elegant as you have not to
recompile but same difficulies after - and you said it's not obvious.
- construct the syntax tree and forward-it  to back-end   OR   pick up
what you can from the back end and do it yourself. and yes :  it's a
long way to go and you'd better have dinner before I'm back :+)