[Pharo-project] Thinking about Pharo distribution
stephane.ducasse at inria.fr
Tue Sep 16 03:19:36 EDT 2008
I agree. Now we can also late bound core boundary. :)
I really believe that we should learn.
If tomorrow somebody come up with a really nice integration of the
package then it can be really core.
On Sep 16, 2008, at 9:02 AM, Adrian Lienhard wrote:
> Stef, maybe you misunderstood me. I don't argue against putting it
> into core...
> But I think it does not make a lot of sense in dev. Only if it is in
> core, methods like #match: can use it.
> On Sep 16, 2008, at 08:54 , Stéphane Ducasse wrote:
>> No this is something else.
>> Look at all the crap in match: and other. I do not think that regex
>> is so large that it is a problem.
>> There are so much other totally ***useless** things in the image
>> that something useful would be really good.
>> What we can do: is give it a try we do not have to be perfect the
>> first time.
>> Having a vision and path to achieve it should not hamper us to try
>> and learn. Look at the use of MC :)
>>> On Sep 16, 2008, at 07:13 , Damien Cassou wrote:
>>>> On Mon, Sep 15, 2008 at 9:45 PM, Adrian Lienhard
>>>> <adi at netstyle.ch> wrote:
>>>>> I agree that we should make it clear what to start with
>>>>> (obviously the dev
>>>>> The list of packages seems ok to me, except for Regex.
>>>> What is your problem with Regex?
>>> I think it should either be in core (as Marcus argues) or in no
>>> distro. The reason is that this is not a development tool but will
>>> be used as a library. Then if you deploy using the core distro,
>>> you have to load it anyway. And if we start to add Regex, why not
>>> also adding an XML parser? and package XYZ? So we end up
>>> accumulating libraries that blow up the image even if they are
>>> used only by few people. I'd like to control myself, which
>>> packages to make part of the application.
>>> Pharo-project mailing list
>>> Pharo-project at lists.gforge.inria.fr
>> Pharo-project mailing list
>> Pharo-project at lists.gforge.inria.fr
> Pharo-project mailing list
> Pharo-project at lists.gforge.inria.fr
More information about the Pharo-dev