OK. I've completed my port from the TridiaVNC Win32 vncviewer code tree to a PocketPC
(CE 3.0) version of TridiaVNC 1.5beta.
This is most directly of interest to the Tridia group, but I didn't know if anyone at
the original ORL labs would be interested in how I worked around the lack of C++
Exception handling in the CE compilers (setjmp/longjmp plus my own multithread-safe
exception frame handling code -- still doesn't properly handle class hierarchies, and
it will NOT call destructors for C++ objects that exited scope because of the
exception, but there isn't any way to do that without access to the internals of the
compiler)
My intent is to provide this in such a way as to ease its integration into the
TridiaVNC CVS tree. Unfortunately, the CE tools also cannot process VC6 project or
workspace files, so I had to make my own (vcp and vcw files, respectively).
I have also called my project OMNIvnc because it relates to the project I am working
on. Since VNCviewer uses a class called omnithread, I also thought this was a nice
synergy, so I named all of my exception handling stuff OMNI_EXC_etc.
So, to the Tridia team - I can think of three options :
1. I can generate a diff file.
2. I can zip or tar the collection up and send it to somebody.
3. I can check it back into CVS (which I am leery of, since I have no idea what effect
it will have on the normal Win32 builds. I tried to be nice, but I might have missed
something)
To the ORL team :
Is there any of this that you would be interested in having?
(Crud, just remembered that my exception handling usage comments are out of date...)
Please advise.
Mac
_____________________________ /"\
Mac Reiter \ / ASCII Ribbon Campaign
Nomadics, Inc. X Against HTML Mail
[EMAIL PROTECTED] / \
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
