I didn't understand exactly what you're proposing.

BTW, have you looked at an mcv file using a text editor? 

I think that it could be converted into valid .cs with a pretty simple
regexp, by someone with no Smalltalk knowledge (just two samples to
compare).

Daniel

Andreas Raab <andreas.raab at gmx.de> wrote:
> If you're going for some fileout-like format (I interpret Ned's message that
> way) then I'd strongly recommend defining and using these stubs. In fact,
> I'd go as far as to say don't make them "MCClassDefinition" but rather some
> app-registry kind of thing. It tells people what interfaces they can rely
> on, it documents (for your own knowledge) what interfaces have been released
> and are used out there and other package/versioning systems could hook into
> the same places if they know how to interpret them. The "default stub" would
> then be the "empty package/versioning system".
> 
> Cheers,
>   - Andreas