On Sun, Mar 6, 2011 at 6:14 AM, Mark Morgan Lloyd
wrote:
> Marcos Douglas wrote:
>
Make a function to return a global variable does not make it read only.
If I use your function like this:
o := InitText;
o := nil; //this is the same xInitText = nil
>>>
>>> Disagree. You are ch
Marcos Douglas wrote:
Make a function to return a global variable does not make it read only.
If I use your function like this:
o := InitText;
o := nil; //this is the same xInitText = nil
Disagree. You are changing the value of o, not of xInitText. xInitText is
initialised once somewhere in th
On Sun, Mar 6, 2011 at 02:14, Marcos Douglas wrote:
> On Sat, Mar 5, 2011 at 7:05 PM, Mark Morgan Lloyd
> wrote:
>> Marcos Douglas wrote:
>>>
>>> On Sat, Mar 5, 2011 at 8:24 AM, Mark Morgan Lloyd
>>> wrote:
Where a unit exports an instance of an object, what's best practice for
ma
On Sat, Mar 5, 2011 at 7:05 PM, Mark Morgan Lloyd
wrote:
> Marcos Douglas wrote:
>>
>> On Sat, Mar 5, 2011 at 8:24 AM, Mark Morgan Lloyd
>> wrote:
>>>
>>> Where a unit exports an instance of an object, what's best practice for
>>> making this read-only? I'm referring to the object reference itsel
On Sat, Mar 5, 2011 at 8:15 PM, Marcos Douglas wrote:
> On Sat, Mar 5, 2011 at 7:05 PM, Mark Morgan Lloyd
> wrote:
>> Marcos Douglas wrote:
>>>
>>> On Sat, Mar 5, 2011 at 8:24 AM, Mark Morgan Lloyd
>>> wrote:
Where a unit exports an instance of an object, what's best practice for
On Sat, Mar 5, 2011 at 7:05 PM, Mark Morgan Lloyd
wrote:
> Marcos Douglas wrote:
>>
>> On Sat, Mar 5, 2011 at 8:24 AM, Mark Morgan Lloyd
>> wrote:
>>>
>>> Where a unit exports an instance of an object, what's best practice for
>>> making this read-only? I'm referring to the object reference itsel
Marcos Douglas wrote:
On Sat, Mar 5, 2011 at 8:24 AM, Mark Morgan Lloyd
wrote:
Where a unit exports an instance of an object, what's best practice for
making this read-only? I'm referring to the object reference itself here,
not properties of the object.
Where I've done this in the past I've u
On Sat, Mar 5, 2011 at 8:24 AM, Mark Morgan Lloyd
wrote:
> Where a unit exports an instance of an object, what's best practice for
> making this read-only? I'm referring to the object reference itself here,
> not properties of the object.
>
> Where I've done this in the past I've used a function:
Where a unit exports an instance of an object, what's best practice for
making this read-only? I'm referring to the object reference itself
here, not properties of the object.
Where I've done this in the past I've used a function:
interface
function InitText: TFormattedString;
implementation
