On Fri, Dec 26, 2014 at 3:49 PM, Sven Barth
wrote:
> Am 23.12.2014 18:11 schrieb "silvioprog" :
> > Hm... my revision is: (*). (from GIT)
> >
> > The output:
> >
> > [14:07:46.689]: TFoo$1$crcB96581A6
> > [14:07:46.690]: TFoo$1$crcB96581A6
> >
> > (*):
> >
> > SHA 05f1c39d
> > by pierre, 23/12/20
Am 23.12.2014 18:11 schrieb "silvioprog" :
> Hm... my revision is: (*). (from GIT)
>
> The output:
>
> [14:07:46.689]: TFoo$1$crcB96581A6
> [14:07:46.690]: TFoo$1$crcB96581A6
>
> (*):
>
> SHA 05f1c39d
> by pierre, 23/12/2014 13:12
> parent 667edc8b
>
> go32v2 must also define NO_THREADING, as thre
And:
C:\repository\git\freepascal\bin\i386-win32>fpc -iDV
2014/12/23 2.7.1
...
begin
WriteLn({$I %FPCDATE%});
end.
Out: 2014/12/23
On Tue, Dec 23, 2014 at 2:10 PM, silvioprog wrote:
> On Tue, Dec 23, 2014 at 1:22 PM, Sven Barth
> wrote:
>
>> Am 23.12.2014 15:53 schrieb "silvioprog" :
>> >
On Tue, Dec 23, 2014 at 1:22 PM, Sven Barth
wrote:
> Am 23.12.2014 15:53 schrieb "silvioprog" :
> > It is very weird this generated class names. The Free Pascal will
> continue to use these weird names or there are plans to improve this in
> future versions? With names like that is almost impossi
Am 23.12.2014 15:53 schrieb "silvioprog" :
> It is very weird this generated class names. The Free Pascal will
continue to use these weird names or there are plans to improve this in
future versions? With names like that is almost impossible to create
automated error logs structures with Free Pasca
Hello,
Recently I've made a class to generate error log for codes in Delphi and
Free Pascal. It works capturing the class name where the problem occurred,
adding the date/time concatenated with the error message. It's working
perfectly in Delphi.
The problem is in Free Pascal and in your approach
