Em 27/01/14 20:39, Marco van de Voort escreveu:
In our previous episode, Joao Morais said:
Hello list. Whenever I add interfaced objects to a
TFPGInterfacedObjectList, those objects apparently add two references,
while release only one when the list is cleaned or destroyed.
v1 reference will on
In our previous episode, Joao Morais said:
>
> Hello list. Whenever I add interfaced objects to a
> TFPGInterfacedObjectList, those objects apparently add two references,
> while release only one when the list is cleaned or destroyed.
v1 reference will only be freed at the end, and also counts
Hello list. Whenever I add interfaced objects to a
TFPGInterfacedObjectList, those objects apparently add two references,
while release only one when the list is cleaned or destroyed.
The following code shows:
==>>>==
$ /tmp/project1
just before vl.add(v1)..: 1
just after vl.
2014-01-27 Michael Van Canneyt
>
> On Mon, 27 Jan 2014, silvioprog wrote:
>
>> 2014-01-26 Michael Van Canneyt
>> On Sun, 26 Jan 2014, silvioprog wrote:
>> Hello,
>>
>> Conforms issue #16043:
>>
>> "ExtractStrings in the Classes unit skips over empty text
Am 2014-01-27 17:41, schrieb waldo kitty:
> well, i can't set any option more than once, anyway... not unless i make a
code error and set or clear the wrong bit but that will be noticed very quickly
during testing ;) for readability, i find setting the bits and then running down
a simple CASE
On 1/27/2014 4:57 AM, Lukasz Sokol wrote:
On 24/01/14 16:20, waldo kitty wrote:
with the above epiphany and some other information i have acquired,
i'm now in the process of rewriting the app... i suspect it will take
me a day or two to get to the point i was at previously with the
operational a
Am 27.01.2014 13:10 schrieb "Michael Van Canneyt" :
>
>
>
> On Mon, 27 Jan 2014, hinst wrote:
>
>>
>> More compiler modes = more complexity = more difficulties for people who
>> support & develop FPC Over time FPC and Delphi modes are becoming
>> increasingly incompatible. I predict that sooner or
On 27 Jan 2014, at 13:11, Michael Van Canneyt wrote:
On Mon, 27 Jan 2014, hinst wrote:
so Delphi mode in
FPC will always mean Delphi 2007 and earlier.
The above is correct.
We will add string=widestring in the next (or next+1) trunk release.
... in {$mode delphiunicode}, which will mean
On Mon, 27 Jan 2014, hinst wrote:
More compiler modes = more complexity = more difficulties for people who
support & develop FPC Over time FPC and Delphi modes are becoming
increasingly incompatible. I predict that sooner or later FPC developers
will have to drop Delphi mode support because
27.01.2014, 15:02, "Fred van Stappen" :
>> Date: Mon, 27 Jan 2014 08:53:25 +0100
>> From: xhaj...@hajny.biz
>> To: fpc-pascal@lists.freepascal.org
>> Subject: Re: [fpc-pascal] Pure FPC ?
>>
>> On Mon, January 27, 2014 01:38, Fred van Stappen wrote:
>> > Ok, i will try to explain better.
>> >
>> > W
> Date: Mon, 27 Jan 2014 08:53:25 +0100
> From: xhaj...@hajny.biz
> To: fpc-pascal@lists.freepascal.org
> Subject: Re: [fpc-pascal] Pure FPC ?
>
> On Mon, January 27, 2014 01:38, Fred van Stappen wrote:
> > Ok, i will try to explain better.
> >
> > When you compile fpc, you do > make clean + make
On 24/01/14 16:20, waldo kitty wrote:
> On 1/23/2014 5:01 AM, Lukasz Sokol wrote:
>
>> Maybe Something like: (but this is with type TOptionMinMax =
>> [mmNone, mmMin,mmMinMax, mmMax])
>
> i wanted to thank you, lukasz, for your input... it has made me take
> another look while rewriting to implem
On Mon, 27 Jan 2014, silvioprog wrote:
2014-01-26 Michael Van Canneyt
On Sun, 26 Jan 2014, silvioprog wrote:
Hello,
Conforms issue #16043:
"ExtractStrings in the Classes unit skips over empty text. For
example:
Yes. This is delphi compatible.
Th
13 matches
Mail list logo
