[Pharo-project] Primitive calls in one package

Schwab,Wilhelm K bschwab at anest.ufl.edu
Sat Feb 5 21:40:41 CET 2011

If there is a problem finding primitives, then that probably deserves attention in the browsers.  Given that collections, sockets, streams, etc. all use primitives, will likely continue to do so, and will also find competition (Nile, new sockets package, etc.), I think it would be inappropriate to set up a presumption that all primitives lurk in one package.  It cannot (or should not) be enforced, and would interfere with evolution.

With respect, -1.


From: pharo-project-bounces at lists.gforge.inria.fr [pharo-project-bounces at lists.gforge.inria.fr] On Behalf Of Laval Jannik [jannik.laval at inria.fr]
Sent: Saturday, February 05, 2011 3:06 PM
To: Pharo Development
Subject: [Pharo-project] Primitive calls in one package


What is your opinion about having all primitive calls in one package ?
It would be easier to maintain and to find them.

Another question: why all existing primitive in VM have not a method in the image ?

Jannik Laval

More information about the Pharo-project mailing list