Does anyone work on the Win32 version?
I have made it compile, also the rtp classes,
but would need some sample code for testing.
Is there any more docs planned in the near
future? Otherwise this seems to be quite useless
if you are not the ultimate hacker.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm thinking that Win32 is a very low priority at this point. I've offered to do some maintenance and add the classes that I had to add for getting my last project going on Win32, (most notably the ThreadLock class for a read/write lock and some TCP stuff), but got no response or indication of interest.
It's too bad, the project architecture looks pretty good at this point, but every project I do has to cross compile on NT/2000 and the gap between the cc++ POSIX classes and the Win32 implementation is growing.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, if I may pinch in, I am interested in those fixes as well. Otherwise, I have to code them myself ;-)
(If I do, I'll send a patch.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2001-02-04
Mark, is there a way to get those fixes from you? I'm in the process of trying to get this code to work on Win32 as well (and it seem that the SocketPort class is missing?). Any help would be most appreciated...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Over time different people have working on maintaining the win32 code in Common C++, but never on a long term or continuing basis. I have been looking for some time to appoint a win32 sub maintainer and there used to be a job posting for it on Sourceforge, though I did not get replies from it. Rossta is currently doing stuff to clean up win32 code, and a lot of his changes will be found in 1.3.3 (or 1.4.0, depending on which designation ends up used). If others wish to help with win32 code, I would be happy to add them to cvs.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I agree with mtutt that win32 code has much lower priority than posix
Today I came across these problems:
1. Some member variables in Thread are not initialized by the default constructor (e.g. _active and _throw). This causes strange behaviour later, during thread execution.
2. Thread::Execute could call (through Yield) longjmp before reaching the call to setjmp. The crash is imminent. Actually this happens if you destroy the thread right after starting it.
3. TCPSocket::getRequest() doesn't seem to work.
I think it should call Socket::getPeer() instead of Socket::getSender().
How could I contribute code to CC++ ?
thanx
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Does anyone work on the Win32 version?
I have made it compile, also the rtp classes,
but would need some sample code for testing.
Is there any more docs planned in the near
future? Otherwise this seems to be quite useless
if you are not the ultimate hacker.
I'm thinking that Win32 is a very low priority at this point. I've offered to do some maintenance and add the classes that I had to add for getting my last project going on Win32, (most notably the ThreadLock class for a read/write lock and some TCP stuff), but got no response or indication of interest.
It's too bad, the project architecture looks pretty good at this point, but every project I do has to cross compile on NT/2000 and the gap between the cc++ POSIX classes and the Win32 implementation is growing.
Well, if I may pinch in, I am interested in those fixes as well. Otherwise, I have to code them myself ;-)
(If I do, I'll send a patch.)
Mark, is there a way to get those fixes from you? I'm in the process of trying to get this code to work on Win32 as well (and it seem that the SocketPort class is missing?). Any help would be most appreciated...
Over time different people have working on maintaining the win32 code in Common C++, but never on a long term or continuing basis. I have been looking for some time to appoint a win32 sub maintainer and there used to be a job posting for it on Sourceforge, though I did not get replies from it. Rossta is currently doing stuff to clean up win32 code, and a lot of his changes will be found in 1.3.3 (or 1.4.0, depending on which designation ends up used). If others wish to help with win32 code, I would be happy to add them to cvs.
I agree with mtutt that win32 code has much lower priority than posix
Today I came across these problems:
1. Some member variables in Thread are not initialized by the default constructor (e.g. _active and _throw). This causes strange behaviour later, during thread execution.
2. Thread::Execute could call (through Yield) longjmp before reaching the call to setjmp. The crash is imminent. Actually this happens if you destroy the thread right after starting it.
3. TCPSocket::getRequest() doesn't seem to work.
I think it should call Socket::getPeer() instead of Socket::getSender().
How could I contribute code to CC++ ?
thanx