--- "William A. Rowe, Jr." <[EMAIL PROTECTED]> wrote: > That's twisted LOL - glad it works!
Me too but I had doubts and I'm afraid it is questionable if it will continue to work in never versions. I assume that appearance of this problem indicates CLR's wish to increase 'management' of data so that, eventually, it would send a deep copy (all pointers unrolled) to unmanaged side and then account for the changes by 'safely' copying them back into 'managed' CLR types. Too bad that OS is full of opaque types (like handles) so that, ultimately, OS itself would need to be rewritten ;) I am looking into warnings like: 'Apache::Web::WorkerRequest::Handler' uses pinning pointers but unwind semantics are not enabled. Consider using /EHsc and LINK : warning LNK4243: DLL containing objects compiled with /clr is not linked with /NOENTRY; image may not run correctly but MSDN explanation of causes and fix for the latter one is not really crystal clear to me. Regarding unwind semantics very helpful MC++ FAQ site says: "In fact, in VC++ 2005 (aka whidbey), mixing /clr (any of it's variants) and /EHs will not be possible; the compiler will require you to especify /EHa instead. Given this, it is a good time to ensure your applications are being compiled now with the appropiate combinations of switches" Site copyright notice is quite old: "Copyright(C) 2002, Tomas Restrepo", so I guess this quotation is legal. Tony __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
