[Mono-list] 3 TODOs in Threading namespace almost completed

Jeroen Frijters jeroen@sumatra.nl
Tue, 16 Mar 2004 23:09:26 +0100


> > Why do assume a particular implementation? Marking a class=20
> sealed and
> > abstract seems like a perfectly sensible way to compile=20
> "static class".
> I think they might have felt that `static' conveys better the=20
> intention. =20

I'm sorry, I wasn't clear. What I meant was: The way to compile "static
class" would be to emit a class that is both abstract and sealed (and
not have a private constructor, like you said).