On Sat, 2010-11-20 at 23:03 +0700, Paul Ishenin wrote:
> 20.11.2010 22:48, Jonas Maebe wrote:
> > It's not about porting code, it's about existing FPC code.
> Changes in interfaces also breaks existing FPC code. And plus adds more
> problems to delphi code porting.
Again, these changes are detect
Jonas Maebe schrieb:
Const is a pascal keyword which can mean for pascal "pass records
by reference".
Making it mean that would make a lot of code less efficient. It
doesn't have that meaning for the i386 "register" calling convention
either (and it cannot be made to mean that there, because t
On 20 Nov 2010, at 17:11, Jonas Maebe wrote:
> On 20 Nov 2010, at 17:03, Paul Ishenin wrote:
>
>> 20.11.2010 22:48, Jonas Maebe wrote:
>>> It's not about porting code, it's about existing FPC code.
>> Changes in interfaces also breaks existing FPC code. And plus adds more
>> problems to delphi
On 20 Nov 2010, at 17:03, Paul Ishenin wrote:
> 20.11.2010 22:48, Jonas Maebe wrote:
>> It's not about porting code, it's about existing FPC code.
> Changes in interfaces also breaks existing FPC code. And plus adds more
> problems to delphi code porting.
Yes, but it's only part of the reason w
20.11.2010 22:48, Jonas Maebe wrote:
It's not about porting code, it's about existing FPC code.
Changes in interfaces also breaks existing FPC code. And plus adds more
problems to delphi code porting.
Best regards,
Paul Ishenin.
___
fpc-devel maillis
Am 20.11.2010 16:43, schrieb Paul Ishenin:
> Moreover those who need to port
> their projects to FPC will need to review their assember anyway because
> as I know assember is not compatible.
Delphi assembler is supposed to work?
___
fpc-devel maillist -
On 20 Nov 2010, at 16:43, Paul Ishenin wrote:
> 20.11.2010 18:52, Jonas Maebe wrote:
>> A few things are being mixed here:
>> 1) all C header translations have to mark the imported routines as "cdecl",
>> and cdecl, cppdecl and mwpascal are the only calling convention where
>> "const" has a def
20.11.2010 18:52, Jonas Maebe wrote:
A few things are being mixed here:
1) all C header translations have to mark the imported routines as "cdecl", and cdecl, cppdecl and mwpascal are the only calling convention
where "const" has a defined meaning in FPC as far as how a parameter is passed (name
Hello,
I like the llvm architecture and want to ask if I can help developing
the llvm code generation for fpc (with the intention to make llvm
fully replace fpc's own asm generation)
Here my questions:
- Who is working on llvm integration?
- What has to be done in the near future?
- Wher
Am 20.11.2010 14:30, schrieb Marco van de Voort:
> In our previous episode, Sergei Gorelkin said:
>>> 2. THandleStream has a field FHandle which is defined as Integer. Now
>>> this handle is filled either by the constructor which takes an Integer
>>> as well or by e.g. TFileStream which gets its
Marco van de Voort пишет:
In our previous episode, Sergei Gorelkin said:
2. THandleStream has a field FHandle which is defined as Integer. Now
this handle is filled either by the constructor which takes an Integer
as well or by e.g. TFileStream which gets its handle from
FileOpen/FileCreate. T
In our previous episode, Sergei Gorelkin said:
> > 2. THandleStream has a field FHandle which is defined as Integer. Now
> > this handle is filled either by the constructor which takes an Integer
> > as well or by e.g. TFileStream which gets its handle from
> > FileOpen/FileCreate. Those return
Sven Barth пишет:
Hello together!
While getting SysUtils and Classes to compile for Native NT I've
stumbled upon some more spots where Handle=LongInt/LongWord is assumed.
1. In objpas/sysutils/filutilh.inc and its implementation
objpas/sysutils/fina.inc the GetFileHandle functions are define
Hello together!
While getting SysUtils and Classes to compile for Native NT I've
stumbled upon some more spots where Handle=LongInt/LongWord is assumed.
1. In objpas/sysutils/filutilh.inc and its implementation
objpas/sysutils/fina.inc the GetFileHandle functions are defined with
return type
On 20 Nov 2010, at 12:21, Paul Ishenin wrote:
> 20.11.2010 17:53, Jonas Maebe wrote:
>> Also, the default calling convention on non-x86 platforms is supposed to be
>> compliant with the default ABI of the platform. Many of these platforms pass
>> small records all by value (const or not).
>
>
20.11.2010 17:53, Jonas Maebe wrote:
Also, the default calling convention on non-x86 platforms is supposed
to be compliant with the default ABI of the platform. Many of these
platforms pass small records all by value (const or not).
Const is a pascal keyword which can mean for pascal "pass rec
On 19 Nov 2010, at 17:56, Paul Ishenin wrote:
> 19.11.2010 23:47, Jonas Maebe wrote:
>>
>> Well, it could be done since "const" is implementation-dependent, but it
>> would force all non-x86 platforms to pass all const parameters by reference
>> by default, which may not be desirable from an e
On Tuesday, 16. November 2010 14.52:12 Paul Breneman wrote:
>
> I'd like to take the minimal distros and add a simple option to use
> MSEide and it supports debugging from what I understand. Then maybe
> extending that with remote debugging would be the next item.
>
MSEide is ready to work with re
18 matches
Mail list logo
