-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oops ?!?! I supposed that using the much greater count of registers
in 64 bit mode could speed up any kind of software. I suppose that
the experts _are _working on that, though.
Registers are only so useful. I have a very nice example program
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It's ugly but have a look at the .inc files. There are ifdefs already,
eg: for beos all over the place.
If we declare a new type, where do we put it?
I don't like this solution. There is no way possible now to have a piece of
code without ifdefs to
And to add to my last setuid stuff.. I think that if we properly audit
the IDE code so that:
a) fpc is called in the uid of the original ide starter
b) the console is run in the uid of the original ide starter
c) compiler programs are called in the uid of the original IDE starter
I think it's ok
I think that together with the debian gpm crap it's safe to flag linux
as a non-target for the IDE and be done with it. It's IMHO not worth
anyone's nerves to try and hit this moving tty/console target anymore...
Ales
___
fpc-devel maillist -
Michael Van Canneyt wrote / napísal(a):
Then where did he get the docs from ? =-)
David Butler wrote / napísal(a):
Actually, Delphi now supports for-in.
It also supports things like nested classes, class helpers, operator
overloading and inlining.
All those features are because of .NET.
FPC supported proper operator overloading (not in classes only) and
inlining for quite
David Butler wrote / napísal(a):
All the same, they are also supported in the Win32 compiler.
What I ment to say is that we're most probably not going to re-do what
we already have done differently before Delphi. eg: I don't see their
OOP operator overloading as viable considering we have a
