> Now, concerning "both fpc and delphi". That Delphi code can be
> compiled with FPC is rather good thing but FPC has not to follow
> Delphi. The future of Pascal is not Delphi, it is FreePascal. And,
> no, for once, I am not joking. :-)
Most users expect the same behaviour in delphi and fpc. We g
On Thu, 28 Jul 2005, L505 wrote:
> | I will check it, although I "prefer" a platform independent aproach.
>
>
> Same .. if anyone knows of other ways to pipe, let us know.
Use TProcess. Works currently on windows and unixes.
See the Lazarus IDE sources for ways how to use it.
Michael.
Peter Vreman a écrit :
Since you ask the question, I suppose you cannot simply
suppress the "movl $0,%edx" line generation [*]. What about
using a compiler directive, something like {$EXTENDEDMUL ON/OFF}
for instance?
I don't like this. This means we have to add directives for all kind of
speci
>>>Since you ask the question, I suppose you cannot simply
>>>suppress the "movl $0,%edx" line generation [*]. What about
>>>using a compiler directive, something like {$EXTENDEDMUL ON/OFF}
>>>for instance?
>>
>> I don't like this. This means we have to add directives for all kind of
>> special cpu
On 29 Jul 2005, at 11:36, Marcel Martin wrote:
But it is a special case because FPC makes it special.
No, it's simply a consequence of the fact that Pascal performs all
calculations using the native integer type by default.
Jonas
___
fpc-pasca
Peter Vreman a écrit :
>Marcel Martin wrote :
Since you ask the question, I suppose you cannot simply
suppress the "movl $0,%edx" line generation [*]. What about
using a compiler directive, something like {$EXTENDEDMUL ON/OFF}
for instance?
I don't like this. This means we have to add directiv
Peter Vreman wrote:
>>Florian Klaempfl a écrit :
>>
>>>Vincent Snijders wrote:
>>>
>>>
>>>
Hi,
Suppose I have the following code:
var
a,b: dword;
c: qword;
begin
a := 1000;
b := 2000;
c := a * b;
writeln(c);
end.
Now
