It makes sense. But in that setting, creating a package named
'Seaside' and beginning to add some Seaside-... packages as required
would be disastrous. No? But maybe I am missing something here...
Cheers,
Alexandre
On 12 Oct 2008, at 11:46, Lukas Renggli wrote:
In Visualworks there is no dash convention, which is much better...
This might be interesting in the context of discussion:
We documented the package naming conventions for Seaside 2.9 here:
http://code.google.com/p/seaside/wiki/PackageNaming
The complete list of packages is documented here:
http://code.google.com/p/seaside/wiki/LoadOrder
When following these conventions there are no conflicts. The dashes
are there to separate the different concerns of the name. We don't use
meta-packages (-All), because every developer has a different set of
packages anyway.
Cheers,
Lukas
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
--
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
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
