Primitive calls in one package

On Mon, Feb 7, 2011 at 3:24 AM, jannik.laval <[hidden email]> wrote:

I understand your point :),
Now, with my problem with Network, we can see that some primitives do not exist in the image of pharo nor squeak.
But are inside etoys image....

:3  I smell we need to open a ticket to remove that!
 

Where I think that all these images should have the same primitives, because based on same VM.
My idea is in that way: how can we maintain primitives and match them with the vm ?

Cheers,
Jannik

On Feb 6, 2011, at 17:47 , Noury Bouraqadi wrote:

> I totally agree with Bill.
>
> Noury
>
> On 5 févr. 2011, at 21:40, Schwab,Wilhelm K wrote:
>
>> 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.
>>
>> Bill
>>
>>
>>
>> ________________________________________
>> From: [hidden email] [[hidden email]] On Behalf Of Laval Jannik [[hidden email]]
>> Sent: Saturday, February 05, 2011 3:06 PM
>> To: Pharo Development
>> Subject: [Pharo-project] Primitive calls in one package
>>
>> Hi,
>>
>> 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 ?
>>
>> Cheers,
>> ---
>> Jannik Laval
>>
>>
>>
>
>