[fpc-pascal] IInterface.QueryInterface, ._AddRef and ._Release definitions have been changed...
Hi! I read http://wiki.freepascal.org/User_Changes_Trunk#IInterface.QueryInterface.2C_._AddRef_and_._Release_definitions_have_been_changed. What's the stable FPC version that will include this changes (if it's not released yet)? I need write a patch to zeoslib, and I want keep compatibility with old versions of fpc. Regards, Fabio ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Libnodave on linux
Maybe, you can try the PascalSCADA...
Regards,
Fabio
2011/2/4 Jonas Maebe :
>
> On 04 Feb 2011, at 21:24, Peter Andersen wrote:
>
>>> That's a very bad way to link libc, because afaik it bypasses all compiler
>>> detections for the fact that you are linking to that library (and doing so
>>> requires using different startup code). Instead, either add {$linklib c} to
>>> the source, or add the "initc" unit to the uses clause.
>>
>> Please could you explain it a little bit more.
>
> What is it exactly that you do not understand?
>
>
> Jonas___
> fpc-pascal maillist - fpc-pascal@lists.freepascal.org
> http://lists.freepascal.org/mailman/listinfo/fpc-pascal
>
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] OPC-DA support
I don't know if here is the right place to request this, but... sorry if I'm wrong. I'm requesting help to support OPC-DA on PascalSCADA. As the target of PascalSCADA is keep the support to multiples platforms (using Lazarus and FPC), I'm thinking to convert the libraries JInterop and Utgard (that works on multiples platforms) to pascal. If are you interested and knows java and pascal, please contact-me (fa...@pascalscada.com)! The best regards Fabio ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] Re: [Lazarus] OPC-DA support
Hi Mr. Soricetti! Yes, OPC-DA uses DCOM, that only works on Windows. But the proposal of JInterop project is provide DCOM layer independently of OS while the project OpenSCADA.Utgard, that uses JInterop, provide the OPC-DA functionality on others OS than Windows. The PascaSCADA project provides direct communication with some devices (Siemens PLC´s and any Modbus RTU/TCP device). So, to improve the list of devices that PascalSCADA can exchange data, I´ll prioritize the implementation of OPC-DA functionality. So, my idea is translate the JInterop and OpenSCADA.Utgard to pascal, to provide OPC-DA functionality for Lazarus/FPC under Windows/Linux and FreeBSD at least. If are you interested, please contact-me! 2011/5/26 Massimo Soricetti : > Il 26/05/2011 20:00, fluisgira...@gmail.com ha scritto: >> I'm requesting help to support OPC-DA (that uses DCOM) on PascalSCADA. >> As the target of >> PascalSCADA is keep the support to multiples platforms (using Lazarus >> and FPC), I'm thinking to convert the libraries JInterop and Utgard >> (that works on multiples platforms) to pascal. If are you interested >> and knows java and pascal, please contact-me (fa...@pascalscada.com)! > > Hello Fabio, I'm studying OPC these days. AFAIK OPC is just for windows: > DCOM is not supported in any other environment other than windows, so if > you want to use it on other platforms you will have to build a library > from scratch. > Maybe you are going to write an OPC package for Lazarus? That would be > really great :-) > > ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Re: Platform independent alternatives
Some years ago, I started the port of my project (PascalSCADA) from Windows to others platforms. I found some issues doing this. I used all resources that the FPC RTL can offer. To thread, I used TThread class. The issues that I found porting this, is that Suspend/Resume don't works on others platforms than Windows. So I rewrite my code to don't use this. Windows messages was replaced by a class that I created to exchange messages between threads, not process. TCriticalSection worked as expected on all platforms, except because it isn't a recursive mutex on unix, like it's on Windows. Again, a little code change to avoid problems. TEvent works as expected on all platforms since FPC 2.4.x. How it was fixed only on FPC 2.4 version AND I want support FPC 2.2.x series, I created my own class of Event, based on changes of TEvent class of FPC. Now my project works fine at least on Windows, Linux and FreeBSD, using the thread support of FreePascal. I avoided to use advanced resources of threading of each OS to keep my project more platform independently as possible. Functions as WaitForSingleObject I'm avoiding to use. The best regards, Fabio 2011/6/24 leledumbo : > Rewrite the threading code with FPC one (i.e. BeginThread - EndThread, or the > more beautiful TThread). WaitForSingleObject... I've never used this, > perhaps SyncObjs and its critical section handler? CloseHandle: depending on > how you open it, close with its correct pair. > > -- > View this message in context: > http://free-pascal-general.1045716.n5.nabble.com/Platform-independent-alternatives-tp4518482p4521676.html > Sent from the Free Pascal - General mailing list archive at Nabble.com. > ___ > fpc-pascal maillist - fpc-pascal@lists.freepascal.org > http://lists.freepascal.org/mailman/listinfo/fpc-pascal > ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
