Robert Jordan wrote:
>
>
> IIRC, MS.NET 1.1 SoapFormatter used to behaves like this.
> So it's possible that Mono's SoapFormatter was not updated
> to match MS.NET 2.0.
>
> Please file a bug with a test case.
>
But that was my point and why I didn't file a bug report at once.
IMHO, mono is
I'm not sure whether this counts as a bug in mono, a bug in .NET or simply an
incompatibility that is acceptable, as it's probably a programming bug on my
part anyway.
Using the SoapFormatter, I output a serializable struct to a pre-opened
FileStream. I then output a second serializable struct t
Jonathan Pryor wrote:
>
> On Wed, 2008-09-03 at 10:33 +0200, Robert Jordan wrote:
>
> Alas, I didn't get any further details, but that was enough for me to
> remove fork() from Syscall: if it can't ever be reliably called, then it
> shouldn't be callable.
>
Sorry about jumping in two months l
