Serial Port Component For Lazarus Project Serial Port Component

Thanks to advice here I have found a serial port component that works in similar ways to the one I have used in Windows, so now I am embarking on the porting task.

In the existing unit the serial port communication component is instantiated in code rather than being dropped on a form.

This will be rather ugly since the comm object FComm is used in many places in the code.

This would involve wrapping 5dpo in a superclass, which translates the used propertiesmethods into 5dpo specifics.

Then I would be able to select the proper one to make based on conditionals inside a different unit from my main unit.

But how would this be done more specifically Is there some description available on making code compatible between Delphi and Lazarus when there are component differences in the two systems as I described above (I dont know if this is off-topic here and should be posted to the fpc list instead, but since GMANE does not yet allow posting to the fpc group I hope you will not be offended by me posting this question here.

It seems like it is both a Lazarus vs Delphi question and one regarding subclassing.) Bo Berglund --.

On Sun, 10 Oct 2010 11:46:43 0200 Post by Bo Berglund I have a rather extensive comm unit created in Delphi for communication with a data acquisition instrument via RS232.

Sprinkle the code with conditionams for DelphiLazarus and use the 5dpo component and its specific calls for Lazarus and the existing code for Delphi.

Post by Bo Berglund But how would this be done more specifically Is there some description available on making code compatible between Delphi and Lazarus when there are component differences in the two systems as I described above There are many ways.

For example: uses IFDEF LCL or use ifdef FPC fpcunit ELSE delphiunit ENDIF; or you can put the whole unit into ifdefs: myserial.pas: IFDEF FPC INCLUDE fpcserial.pas ELSE INCLUDE delphiserial.pas ENDIF Post by Bo Berglund (I dont know if this is off-topic here and should be posted to the fpc list instead, but since GMANE does not yet allow posting to the fpc group I hope you will not be offended by me posting this question here.

It seems like it is both a Lazarus vs Delphi question and one regarding subclassing.) Mattias --.

On Sun, 10 Oct 2010 12:03:42 0200, Mattias Gaertner Post by Mattias Gaertner On Sun, 10 Oct 2010 11:46:43 0200 Post by Bo Berglund But how would this be done more specifically Is there some description available on making code compatible between Delphi and Lazarus when there are component differences in the two systems as I described above uses IFDEF LCL or use ifdef FPC fpcunit ELSE delphiunit ENDIF; IFDEF FPC INCLUDE fpcserial.pas ELSE INCLUDE delphiserial.pas ENDIF I am trying to make a wrapper for the sdpoSerial so it will mimick the TSerial I am using in Delphi.

With the conditionals in place Delphi with use unit Serial and Lazarus unit SerialLazarus (the wrapper): uses IFDEF LCL or use ifdef FPC SerialLazarus, ELSE Serial, ENDIF One question though: I need to enter this at the top of my big unit to stop LazarusFPC from complaining about syntax errors: MODE Delphi But if this is detected by Delphi it will complain that there is no MODE command, so can I legally do this: IFDEF FPC MODE Delphi ENDIF (I.e.

Bo Berglund Developer in Sweden --.

You can also write all those settings into an.inc file and just include that at the top of your unit (e.g.

I compilerswitches.inc); this works in both FPC and Delphi and so you have the same settings in all your units where you include that file (of course you need to include the ifdef fpc inside the include file).

On Sun, 10 Oct 2010 17:52:46 0200, Sven Barth Post by Sven Barth Post by Bo Berglund (I.e.

Yes, that is perfectly legal and even necessary if you use multiple compilers.