[fpc-pascal] Re: different windows/linux behavior with enumerated types and write/writeln

2010-01-20 Thread Seth Grover
> Different compiler version. The above is only possible as of 2.4.0. I'm sorry, I should have realized my Windows environment wasn't as up-to-date as my Linux environment. You're absolutely right. Thanks, -SG -- This email is fiction. Any resemblance to actual events or persons living or dead

Re: [fpc-pascal] different windows/linux behavior with enumerated types and write/writeln

2010-01-20 Thread Marco van de Voort
In our previous episode, Jonas Maebe said: > > In other words, it actually prints out the name of the enumerated value. > > > > In windows the program does not compile with an error of "Error: Can't > > read or write variables of this type". > > > > Why the difference in behavior? > > Different

Re: [fpc-pascal] different windows/linux behavior with enumerated types and write/writeln

2010-01-20 Thread Jonas Maebe
On 20 Jan 2010, at 20:07, Seth Grover wrote: > In other words, it actually prints out the name of the enumerated value. > > In windows the program does not compile with an error of "Error: Can't > read or write variables of this type". > > Why the difference in behavior? Different compiler ver

[fpc-pascal] different windows/linux behavior with enumerated types and write/writeln

2010-01-20 Thread Seth Grover
If I have a program like this: -- program Project1; {$mode objfpc}{$H+} type whatever = (seth, paul, ken); var haha : whatever; begin haha := seth; writeln(haha); end. -- I can compil

Re: [fpc-pascal] Pointer to an array of PChar strings

2010-01-20 Thread Graeme Geldenhuys
2010/1/19 Marco van de Voort : > > where cfree is the free() corresponding to the malloc with which it was > allocated in the lib. (usually libc's) Thanks for the repy. In the end I found the library I was using was old. The newer library has a function that does the free'ing of that list for me.