On 02/28/2014 02:18 AM, Hans-Peter Diettrich wrote:
So the lack of Self seems to apply to static; methods, not to
class methods. I'll ask in an EMBT group for a description of
static;, the OH seems to reflect the C++ meaning only,
In ANSI C static with functions just means unreachable from
Am 28.02.2014 09:12 schrieb Michael Schnell mschn...@lumino.de:
On 02/28/2014 02:18 AM, Hans-Peter Diettrich wrote:
So the lack of Self seems to apply to static; methods, not to
class methods. I'll ask in an EMBT group for a description of static;,
the OH seems to reflect the C++ meaning
Michael Schnell schrieb:
On 02/28/2014 02:18 AM, Hans-Peter Diettrich wrote:
So the lack of Self seems to apply to static; methods, not to
class methods. I'll ask in an EMBT group for a description of
static;, the OH seems to reflect the C++ meaning only,
In ANSI C static with functions
On 12/02/14 12:20, Sven Barth wrote:
Am 12.02.2014 10:01, schrieb patspiper:
On 12/02/14 10:03, Sven Barth wrote:
Am 11.02.2014 23:19, schrieb Mattias Gaertner:
Hi,
How does the compiler (2.6.2, 2.6.4, 2.7.1) search for sub tools like
fpcres?
For example: first in its working directory,
Hi,
Consider the following program (compiled using revision 26807 on OSX):
===
Program QWordToExtended;
Begin
WriteLn(Sizeof(Extended));
WriteLn(Sizeof(QWord));
WriteLn(Sizeof(Longword));
WriteLn(Extended(QWord($)));//1
On 28 Feb 2014, at 20:21, Ewald wrote:
WriteLn(Extended(QWord($)));//1
WriteLn(Extended($)); //2
WriteLn(Extended(Longword($))); //3
WriteLn(Extended($));
On 28 Feb 2014, at 20:39, Jonas Maebe wrote:
On 28 Feb 2014, at 20:21, Ewald wrote:
Since I was curious as to the intended-ness of this behaviour I wrote the
second set of tests which show me that this is not true for longwords: both
3 4 give the same result. This lead me to the
On 28 Feb 2014, at 21:07, Ewald wrote:
On 28 Feb 2014, at 20:39, Jonas Maebe wrote:
All hexadecimal constants are (conceptually) parsed as int64, so this is by
design. int64($) is not -1.
So all numeric constants that are not floats are parsed as Int64's?
They are
On 28 Feb 2014, at 23:43, Jonas Maebe wrote:
On 28 Feb 2014, at 21:07, Ewald wrote:
On 28 Feb 2014, at 20:39, Jonas Maebe wrote:
All hexadecimal constants are (conceptually) parsed as int64, so this is by
design. int64($) is not -1.
So all numeric constants that
Ewald schrieb:
On 28 Feb 2014, at 20:39, Jonas Maebe wrote:
All hexadecimal constants are (conceptually) parsed as int64, so
this is by design. int64($) is not -1.
By the way, what do you do when you want to port fpc to a one's
comlement machine (if they still exist)?
10 matches
Mail list logo
