Re^6: Calling a function form an external DLL with Inline::C on windows

Win32::SerialPort uses Win32::CommPort which uses Win32::API to export some functions from the Windows API.

Where does Win32::SerialPort enter into the equation? The original question specifies that the communication is via TCP/IP, not serial.

If there is something I missed...

Comment on Re^6: Calling a function form an external DLL with Inline::C on windows

Replies are listed 'Best First'.
Re^7: Calling a function form an external DLL with Inline::C on windows by kikuchiyo (Hermit) on Aug 12, 2010 at 08:57 UTC
Sorry for replying so late, I wasn't following the thread anymore. Win32::SerialPort comes in because there are other components of my application beside the data readout that uses TCP/IP: one of these components uses serial communication to drive a positioning system. But I was mistaken about the purported incompatibility between Inline::C and Win32::SerialPort, they work together just fine. It was I who introduced a subtle bug in my program that caused those error messages. Sorry for the confusion.	[reply]
Re^8: Calling a function form an external DLL with Inline::C on windows by Anonymous Monk on Feb 13, 2015 at 22:11 UTC
Care to elaborate on the bug you introduced? I am having that same issue trying to move a code base back to windows after a few years away from it.	[reply]