> - We have shipped the source code, anybody can implement it and share
> the implementation with the community.
>
There was a thread on this idea a while back--is there a centralized place
by which to share these fixes? Has Microsoft come up with that yet, or is
this list it, for the moment?
Ted Neward
{.NET || Java} Course Author & Instructor, DevelopMentor
(http://www.develop.com)
http://www.javageeks.com/tneward
http://www.clrgeeks.com/tneward
----- Original Message -----
From: "Jan Kotas" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 01, 2002 12:30 PM
Subject: Re: [DOTNET-ROTOR] SEH Interop via PAL - .NET vs Rotor
> There are many possible answers to this one. If I have to pick two,
> they will be:
>
> - We are focused on portability. The exceptions interop is not
> portable in general, so it is not a priority for us.
>
> - We have shipped the source code, anybody can implement it and share
> the implementation with the community.
>
> -Jan
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> -----Original Message-----
> From: Cristian Diaconu [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 01, 2002 10:40 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [DOTNET-ROTOR] SEH Interop via PAL - .NET vs Rotor
>
>
> Actually, another question...
>
> If PAL_LocalFrame() does provide the fix, why doesn't Rotor use it?
>
> Cristian
>
