in reply to Re^5: Win32::SerialPort ; close / open problem
in thread Win32::SerialPort ; close / open problem

Yeah, I noticed this sort of shenanigans with the last chip I was working with alright. Quite complicated so it is. In fact I suspect that it wasn't quite working properly, as every now and again it would bork spectacularly and in ways that are very much not like what it says on the tin.
It wasn't a massive deal, since we were still prototyping, so I let it slide, and crossed my fingers when investor eyes were on me.
There are many potential points of failure in these setups, not least of which was my dodgy modified Linux driver.
I will indeed let you know how it shapes up.
Here, do you mind me asking, (I will make the assumption you too are also coding up for Win32 machines) why are you using C++, and not C# to solve your problem? That was going to be my next port of call for the production code. You appear to have quite a lot of control over whats happening from the brief look I had.
  • Comment on Re^6: Win32::SerialPort ; close / open problem

Replies are listed 'Best First'.
Re^7: Win32::SerialPort ; close / open problem
by GrandFather (Saint) on Jul 26, 2009 at 20:44 UTC

    Under Windows, for various reasons, any kernel mode code must be written in C (not even C++) and we use C++ as our main production language.


    True laziness is hard work