I am working on an application that will make heavy use of serial communication. I need to deploy on Windows systems first, but subsequent development will be needed to port it to other systems, most likely Linux and Solaris.
Are Win32::SerialPort and Device::SerialPort my best option for portability? Or should I plan on using my own object to hide the varying Serial interfaces from my main code? For Unix systems, should I be opening my own filehandles and such or is there a module that is particularly good?
If anyone cares, I am going to be uploading intel hex files to a firmware flashing program. Because of hardware limitations, I need to chop the big hexfile into many little pieces and load each piece individually. While I can do this with a simple script and a terminal, it is no fun. Thus my desire to automate. Plus, we need a tool to give to our customers (if we ever finish the device and anyone ever buys it).
Update:Added CPAN tags to module names.
TGI says moo
In reply to Portable serial communication by TGI
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |