[fpc-devel]Hi for first time, and a question about tokens.pas

469409 at ingtt.unizar.es 469409 at ingtt.unizar.es
Thu May 31 10:08:21 CEST 2001

> Here it's working correct. Did you delete the .ppu files first and then 
recompiled the
> compiler?

Yes, I always do that not to have problems. I think... repite error I haven't 
it any more but... there some parts of the code (My new rtl) that doesn't 
understand AND token, and I don't know why, does it matter the operators order 
in token const declared in tokens.pas?

If it does, Why ASSIGNMENT is the last token if it has only length 2. 

Can I declare a TOKEN of length 1 such as "y" or "o"?

I've seen that the assambler words are defined in other file something as 
att386.inc (I dont remember very well the name). Is this the only place where 
to change the "assambler tokens".

Is there any place (I think I've seen it but I'm not sure) where there are 
defined some assembler tokens in order to assemble the file generated by this 
program with an external assembler? I want to know it not to change it.

I don't know... how have you managed to know if it detected "repite" that's to 

The first thing I do is change tokens.pas and recompile the compiler, and then
I try to compile a very easy file (writing hello in screen) but it doesn't 
compile it automatically, it needs system unit, and many others in inc and 
i386. And so... these files have to have the new tokens, that's to say, 

I have to put unidad instead of unit. Programa instead of program and this with 
a lot of files.

You seem to have made it easier. How have done it? Because myself I had to 
made a program (www.geocities.com/beatlesnap/pashis.zip) in order to translate 
the basic rtl into my new tokens rtl.

If you have a better way of compiling the compiler without losing 
interpretation of my new tokens, PLEASE TELL ME. Perhaps I've been wasting my 

Take your time. I dont know your self, but my June exams are very near.

Thanks for all,

This message was sent using Endymion MailMan.

More information about the fpc-devel mailing list