GemStone (GLASS) will be writing and reading "old-style" mcz files for the foreseeable future, so backward compatibility is important. Dale ----- "Lukas Renggli" <renggli@gmail.com> wrote: | > Â Â Â Â Â Â Â Â - idea: we keep the * notation but we hook into the | tools to | > Â Â Â Â Â Â Â Â create real package. In particular the user could | either explicitly | > add a method extension | > Â Â Â Â Â Â Â Â to a package or use the* notation. The end result | should be the star | > notation in the cat | > Â Â Â Â Â Â Â Â and the use of a real package in the background. | | It would be nice if old packages could be imported and new ones | merged | and exported without problems. If a package is named "Foo", then its | categories would be represented in Monticello as | "Foo-OriginalCategoryName" and its protocols as | "*foo-OriginalProtocolName". This would allow full compatibility. | | > Â Â Â Â platform could be a problem. So lukas do you if VW uses the | * | > convention, I imagine at least when | > Â Â Â Â saving code? | | Yes, they use the same convention. Categories are not really visible | in VW, but they are the same as on the Pharo side. The package name | could actually be cropped from the protocol, but they strangely don't | do that and still display the *. | | Cheers, | Lukas | | | -- | Lukas Renggli | http://www.lukas-renggli.ch | | _______________________________________________ | Pharo-project mailing list | Pharo-project@lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project