{$MODE MINE} would suit as well :-)
2013/3/6 Thaddy
> {$MODE SUBJECTIVE} is more appropriate in this discussion.
>
> But i am by -first - education a political scientist.
>
>
> On 6-3-2013 15:44, Michael Schnell wrote:
>
>> On 03/06/2013 02:37 PM, Sven Barth wrote:
>>
>>> What exactly do you me
On 2013-03-06 13:13, Alexander Klenin wrote:
On Wed, Mar 6, 2013 at 10:00 PM, Michael Schnell wrote:
On 03/05/2013 05:17 PM, Alexander Klenin wrote:
1) Make sure "is" and "as" work with generic types -- maybe they already
are?
"is" the generic type and/or "is" a certain specialization ?
Yes,
time make -j 64
==
It might not build modules - which present a lot of files thsu I/O.
"make -j .. deb-pkg" builds & packs both image & modules (the
benchmark has selected for build approx 75% of all available modules )
___
fpc-devel m
make -j has a dramatic effect on an SMP system, particularly if it can
find groups of jobs without too much interdependence.
=
The benchamark was surprising. Diring it, me observed 80..95% load of
each CPU still having high I/O load on the RAID1. How can it be ?!
Whi
{$MODE SUBJECTIVE} is more appropriate in this discussion.
But i am by -first - education a political scientist.
On 6-3-2013 15:44, Michael Schnell wrote:
On 03/06/2013 02:37 PM, Sven Barth wrote:
What exactly do you mean?
we already have:
{$MODE FPC}
{$MODE OBTP}
{$MODE DELPHI}
{$MODE OBJFP
Am 06.03.2013 15:19, schrieb Graeme Geldenhuys:
On 2013-03-05 13:02, Sven Barth wrote:
Two words: backwards compatibility.
To Turbo Pascal yes (ie: tp mode), but surely not ObjFPC?
You must not forget that mode ObjFPC isn't the youngest one either. If
we'd freshly design that mode I'd agree wi
On 03/06/2013 02:37 PM, Sven Barth wrote:
What exactly do you mean?
we already have:
{$MODE FPC}
{$MODE OBTP}
{$MODE DELPHI}
{$MODE OBJFPC}
{$MODE OBJMAC}
if {$MODE OBJMAC} not already is for objective Pascal there could be
something like
{$MODE OBJECTIVE}
-Michael
On 2013-03-05 13:02, Sven Barth wrote:
>>
> Two words: backwards compatibility.
To Turbo Pascal yes (ie: tp mode), but surely not ObjFPC?
Regards,
- Graeme -
--
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/
_
Am 06.03.2013 14:35, schrieb Michael Schnell:
On 03/06/2013 01:45 PM, Sven Barth wrote:
There is a mode that's compatible to Mac Pascal, but the Objective
Pascal is independant of the mode, but is triggered by a modeswitch
(as it was specially developed by the FPC and the Mac Pascal
communitie
Am 06.03.2013 14:29, schrieb Michael Schnell:
On 03/06/2013 01:43 PM, Sven Barth wrote:
And how does one the "current" TThread?
Since a few weeks: TThread.CurrentThread ;)
This does in fact use a threadvar:
threadvar
{ the instance of the current thread; in case of an external thread
t
On 03/06/2013 01:45 PM, Sven Barth wrote:
There is a mode that's compatible to Mac Pascal, but the Objective
Pascal is independant of the mode, but is triggered by a modeswitch
(as it was specially developed by the FPC and the Mac Pascal
communities).
Would it not be nice and more straightfor
On 03/06/2013 01:43 PM, Sven Barth wrote:
And how does one the "current" TThread?
Since a few weeks: TThread.CurrentThread ;)
This does in fact use a threadvar:
threadvar
{ the instance of the current thread; in case of an external thread
this is
Nil until TThread.GetCurrentThread w
On Sunday 03 March 2013 18:35:53 Martin Schreiber wrote:
> On Friday 01 March 2013 18:33:56 Martin Schreiber wrote:
> [...]
> On Linux, same computer, OpenSUSE 12.2, comparison FPC 2.6.2, Kylix 3
A last one, simple MSEgui demo, one form, a fancy tlabel, one button:
http://mseide-msegui.sourceforge
Am 06.03.2013 11:57, schrieb Michael Schnell:
On 03/05/2013 08:52 PM, Graeme Geldenhuys wrote:
Good thing is, most of these are kept in the 'delphi' compiler mode.
The 'objfpc' mode normally get some more pascal love.
+1
AFAIK there is an Apple specific Objective Pascal mode, as well. I
think
Am 06.03.2013 11:45, schrieb Florian Klaempfl:
Conclusion:
With FPC, the optimization of threadvar access is not necessary. Instead
it is highly recommended to always use thread specific instances of the
classes that do the threaded work. TThread of course provides this out
of the box.
And
On Wed, Mar 06, 2013 at 10:50:10AM +0100, Daniël Mantione wrote:
>
>
> Op Tue, 5 Mar 2013, schreef Henry Vermaak:
>
> >Damn. My custom config kernel compiles stable kernels in 3-5 minutes on
> >a quad core Xeon, which isn't bad. Did you build with the standard
> >config?
>
> What is the stand
On 03/06/2013 11:45 AM, Florian Klaempfl wrote:
So (as with all x86 variants) no library
or system call is necessary.
Wrong. This is not true in the general case, please read the
appropriate api documents.
I do know that on Windows it's documented like this by Microsoft. But I
also know that
On Wed, Mar 6, 2013 at 10:00 PM, Michael Schnell wrote:
> On 03/05/2013 05:17 PM, Alexander Klenin wrote:
>>
>> 1) Make sure "is" and "as" work with generic types -- maybe they already
>> are?
>
> "is" the generic type and/or "is" a certain specialization ?
Yes, and also generic parameters.
proce
On 03/06/2013 01:54 AM, Frank Church wrote:
I have observed a lot of Delphi developers who have written code that
needs or depends on the features like anonymous methods, generics,
RTTI
or Strings :-[
give up porting to FPC because it proved too difficult, but then
it turns out those libraries
On 03/05/2013 05:17 PM, Alexander Klenin wrote:
1) Make sure "is" and "as" work with generic types -- maybe they
already are?
"is" the generic type and/or "is" a certain specialization ?
-Michael
___
fpc-devel maillist - fpc-devel@lists.freepascal.
On 03/05/2013 08:52 PM, Graeme Geldenhuys wrote:
Good thing is, most of these are kept in the 'delphi' compiler mode.
The 'objfpc' mode normally get some more pascal love.
+1
AFAIK there is an Apple specific Objective Pascal mode, as well. I think
it's really nice to have multiple compilers in
Am 06.03.2013 11:12, schrieb Michael Schnell:
So (as with all x86 variants) no library
or system call is necessary.
Wrong. This is not true in the general case, please read the appropriate
api documents.
With Cortex, this has changed to the use of the CP15 Register (freeing
A9 to allow for
On 03/04/2013 12:47 PM, Michael Schnell wrote:
In all fpc enabled patforms I examined (X86 Windows, X86 Linux, X64-64
Windows, X86-64 Linux, ARM Linux (32 Bits) the platform provides as
well library calls as dedicated threadvar pointer registers. In
windows the registers seem to be undocument
Op Tue, 5 Mar 2013, schreef Henry Vermaak:
Damn. My custom config kernel compiles stable kernels in 3-5 minutes on
a quad core Xeon, which isn't bad. Did you build with the standard
config?
What is the standard config? As the operating system is Scientific Linux
6, I'm using the config fo
Am 05.03.2013 14:02, schrieb Sven Barth:
You can disable this construct with:
http://www.freepascal.org/docs-html/prog/progsu42.html
This should be the default in ObjFpc mode.
Two words: backwards compatibility.
For every version of fpc exists an user changes list, containing items
which b
On 22 Feb 2013, at 13:30, to...@ump.edu.pl wrote:
s1,s2: extended;
s1:=291.022;
s2:=roundto(s1,-30); //TRoundToRange = -37..37;
give me Invalid floating point operation.
I see that roundto goes to single instead of extended. But why ?
Because overload selection is based on parameter matc
26 matches
Mail list logo
