On Sun, Nov 29, 2009 at 1:11 PM, Jonas Maebe wrote:
>
> On 29 Nov 2009, at 16:51, Anthony Walter wrote:
>
>> Having said all that, Jonas, what is the actual implemented behaviour
>> of FPC? Does it 0 initialize heap memory at startup or not?
>
> I guess you mean global data rather than heap (heap
On Sat, Nov 28, 2009 at 7:12 AM, Jürgen Hestermann
wrote:
>> And there are many reasons why there are so many string types nowadays.
>
> True.
>
>> Simply use {mode objfpc}{$h+} like lazarus suggests.
>
> I think the root cause of all these problems are generic types. They cause
> more trouble tha
In our previous episode, Jonas Maebe said:
> >> anything to say on the subject is patently false.
> >
> > As per what? OS ABI? Delphi rules?
>
> As per the linked Delphi documentation. But as has mentioned before, the
> Delphi documentation doesn't match its implementation in case of cdecl and
>
On 30 Nov 2009, at 10:29, Marco van de Voort wrote:
> In our previous episode, Anthony Walter said:
>> Martin Schreiber also chimed in, pointing out:
>>
>> http://bit.ly/6uaAiB
>>
>> "Larger sets, records, and static arrays are passed as 32-bit pointers
>> to the value."
>>
>> The documentatio
In our previous episode, Anthony Walter said:
> > "Allows" is not the same as "forces". This line in the help file does not
> > say that const parameters are passed by reference. It says that it may often
> > be so, perhaps all current implementations make it so, but it is by no means
> > guarantee
