Re: [fpc-devel] How are short/ansi strings implemented ?

2011-04-18 Thread Michael Schnell
On 04/16/2011 02:06 PM, Skybuck Flying wrote: 2. I can also imagine a situation where the compiler would first be string-less Of course, as ANSI C does not have strings. But this is not handy at all. -Michael ___ fpc-devel maillist -

Re: [fpc-devel] Extended type

2011-04-18 Thread Daniël Mantione
Op Mon, 18 Apr 2011, schreef Hans-Peter Diettrich: Sven Barth schrieb: On Windows 64-bit you must not use the x87 FPU, because Microsoft wants it so. Can you be a bit more concrete? Originally MS spread info it wouldn't work at all under Windows, but that proved to be false, the FPU

Re: [fpc-devel] Extended type

2011-04-18 Thread Jonas Maebe
On 18 Apr 2011, at 10:13, Daniël Mantione wrote: Originally MS spread info it wouldn't work at all under Windows, but that proved to be false, the FPU works technically. Now MS just states it is unsupported. And deprecated:

Re: [fpc-devel] Extended type

2011-04-18 Thread Hans-Peter Diettrich
Jonas Maebe schrieb: On 18 Apr 2011, at 10:13, Daniël Mantione wrote: Originally MS spread info it wouldn't work at all under Windows, but that proved to be false, the FPU works technically. Now MS just states it is unsupported. And deprecated:

[fpc-devel] GetEnumValue result type

2011-04-18 Thread Leonardo M . Ramé
Hi, I'm having some trouble if I want to pass an enumerated type as a function parameter, when I get that type with GetEnumValue. For example, if I have this type: TMyType = (mtOne, mtTwo, mtThree); var lMyType: TMyType; begin lMyType := TMyType(GetEnumValue(TypeInfo(TMyType), 'mtTwo'));

Re: [fpc-devel] GetEnumValue result type

2011-04-18 Thread Hans-Peter Diettrich
Leonardo M. Ramé schrieb: TMyType = (mtOne, mtTwo, mtThree); var lMyType: TMyType; begin lMyType := TMyType(GetEnumValue(TypeInfo(TMyType), 'mtTwo')); // lMyType is 1 instead of mtTwo How do you know? Since ord(mtTwo)=1, you seem to be fooled by the debugger. DoDi