Re: [fpc-devel] delphi compatibility issues

2007-05-25 Thread Flávio Etrusco
> Ow ? > I've coded a lot if interfaces with D6 and luckily it complained if I > forgot to implement some of them. > OTOH if the "abstract" keyword for classes was introduced/implemented in FPC it would be nice to have "partial interface implementation" just like Java ;-) Cheers, Flávio ___

Re: [fpc-devel] delphi compatibility issues

2007-05-25 Thread Mario R. Carro
On Friday 25 May 2007, Marc Weustink wrote: > Mario R. Carro wrote: > > Hi, I'm trying to compile the JCL with FreePascal (the common, unix and > > vcl folders). Excluding the portability errors in the JCL, I found some > > issues that I think could be best solved by FPC (and benefit the porting >

Re: [fpc-devel] x86_64 linking issue (2.1.4)

2007-05-25 Thread Alan Krause
Jonas Maebe wrote: It's a bug in the compiler. Please submit a bug report with a compilable sample that demonstrates the problem. Jonas, Thanks much for the reply. I will submit a bug report ASAP. I spent most of the morning trying to simplify the error case, and came up with the following:

Re: [fpc-devel] x86_64 linking issue (2.1.4)

2007-05-25 Thread Jonas Maebe
On 25 mei 2007, at 18:50, Alan Krause wrote: The problem arises when the linker attempts to put all the pieces together into one .so : /usr/bin/ld: uCUNASP_CLCalc.o: relocation R_X86_64_32S against `U_UCUNASP_CLCALC_CUNASPCLSET' can not be used when making a shared object; recompile with

Re: [fpc-devel] delphi compatibility issues

2007-05-25 Thread Marc Weustink
Mario R. Carro wrote: Hi, I'm trying to compile the JCL with FreePascal (the common, unix and vcl folders). Excluding the portability errors in the JCL, I found some issues that I think could be best solved by FPC (and benefit the porting of any other Delphi project also). I'm using FPC from SV

[fpc-devel] x86_64 linking issue (2.1.4)

2007-05-25 Thread Alan Krause
I posted a similar email to the fpc-pascal mailing list, but I am guessing that since the issue is somewhat complex, someone on this list might have a better understanding of what the underlying issue might be. I have successfully ported a Delphi DLL to a compiled shared library under 32-bit l

Re: [fpc-devel] delphi compatibility issues

2007-05-25 Thread Jonas Maebe
On 25 mei 2007, at 15:23, Mario R. Carro wrote: - Some assembler does not compile. For example this function, in JclLogic.pas: procedure SetBitBuffer(var Value; const Bit: Cardinal); asm BTS[Value], Bit end; This unit can be compiled with FPC defining PUREPASCAL but with degraded p

[fpc-devel] delphi compatibility issues

2007-05-25 Thread Mario R. Carro
Hi, I'm trying to compile the JCL with FreePascal (the common, unix and vcl folders). Excluding the portability errors in the JCL, I found some issues that I think could be best solved by FPC (and benefit the porting of any other Delphi project also). I'm using FPC from SVN (updated daily). He

Re: [fpc-devel] Error: Argument can't be assigned to

2007-05-25 Thread Jonas Maebe
On 25 mei 2007, at 11:45, Graeme Geldenhuys wrote: Compiling it with FPC 2.3.1 (Revision: 7448) using ppc386 -S2cgi -OG1 -gl -vewnhi -l -Fu../ -Fu. -FUlib/i386-linux/ fpgfxpackage.pas ..I get the following errors. Any ideas why? fpGUI/gfx/x11/gfx_x11.pas(798,8) Error: Argument can't be assi

Re: [fpc-devel] Error: Argument can't be assigned to

2007-05-25 Thread Micha Nelissen
Graeme Geldenhuys wrote: - code where error occurs --- case Attr.Depth of 1: PixelFormat.FormatType := ftMono;// <-- line 798 4: PixelFormat.FormatType := ftPal4; public propertyPixelFormat: TGfxPixelFormat read FPixelFormat; You only allow read access to

[fpc-devel] Error: Argument can't be assigned to

2007-05-25 Thread Graeme Geldenhuys
Hi, I thought I would try out FPC 2.3.1 (Revision: 7448) and compile fpGUI. Compiling fpGUI with 2.0.5 and 2.1.3 works 100% Compiling it with FPC 2.3.1 (Revision: 7448) using ppc386 -S2cgi -OG1 -gl -vewnhi -l -Fu../ -Fu. -FUlib/i386-linux/ fpgfxpackage.pas ..I get the following errors. Any i

Re: [fpc-devel] Bringing back fpc 2.3.1 to BeOS

2007-05-25 Thread Florian Klaempfl
Marco van de Voort schrieb: >> Peter Vreman a ?crit : >>> Thanks, the patches are applied. One small change in ttyname.inc to use >>> {$ifndef beos} instead of >>> disabling the code for all platforms. >>> >> Oups ! I forgot this one. This is why code review is important. >> >> After updating m

Re: [fpc-devel] Bringing back fpc 2.3.1 to BeOS

2007-05-25 Thread Marco van de Voort
> Peter Vreman a ?crit : > > Thanks, the patches are applied. One small change in ttyname.inc to use > > {$ifndef beos} instead of > > disabling the code for all platforms. > > > Oups ! I forgot this one. This is why code review is important. > > After updating my working copy, i found that i