Re: [fpc-pascal] Preprocessor

2009-12-04 Thread Jonas Maebe
On 04 Dec 2009, at 21:37, ik wrote: > Is there a way to see a preprocessor of what fpc creates rather then the > assembly code so I could see how defines and ifdefs executes (when compiling > rtl) ? No, but you can compile with -vc and then the compiler will print for each conditional whether i

[fpc-pascal] Preprocessor

2009-12-04 Thread ik
Hello, Is there a way to see a preprocessor of what fpc creates rather then the assembly code so I could see how defines and ifdefs executes (when compiling rtl) ? Thanks Ido http://ik.homelinux.org/ ___ fpc-pascal maillist - fpc-pascal@lists.freepas

Re: [fpc-pascal] Setlength

2009-12-04 Thread Jonas Maebe
On 04 Dec 2009, at 17:03, Flávio Etrusco wrote: On Fri, Dec 4, 2009 at 12:32 PM, Jonas Maebe > wrote: On 04 Dec 2009, at 14:57, Carsten Bager wrote: I have 2 lines of code 1 I allocate memory 2 I read from the screen (Nano-X) and save it in the "BitMapArray". Can I do this or can I not be s

Re: [fpc-pascal] Setlength

2009-12-04 Thread Jonas Maebe
On 04 Dec 2009, at 14:57, Carsten Bager wrote: I have 2 lines of code 1 I allocate memory 2 I read from the screen (Nano-X) and save it in the "BitMapArray". Can I do this or can I not be sure that the memory is in one block. I have no idea whether that is guaranteed. It is currently impleme

[fpc-pascal] Setlength

2009-12-04 Thread Carsten Bager
I have 2 lines of code 1 I allocate memory 2 I read from the screen (Nano-X) and save it in the "BitMapArray". Can I do this or can I not be sure that the memory is in one block. setlength(BitMapArray,Width*Height); GrReadArea(TNxWindow(window).w,Left,Top,Width,Height,@BitMapArray[0]); Carsten

Re: [fpc-pascal] can the output object filename be specified on the command line?

2009-12-04 Thread Jonas Maebe
On 04 Dec 2009, at 05:02, Bruce Bauman wrote: Will it cause problems if the unit name (e.g. unit foo__bar;) doesn't match the source filename? I want to source filename to remain unchanged (e.g. bar.pas), but the unit name (and .ppu and .o filenames) to be different (e.g. foo__bar.o, foo