[ANN]

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
26 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: [ANN]

Peter Hugosson-Miller
On Fri, Sep 4, 2009 at 9:38 AM, Stéphane Ducasse <[hidden email]> wrote:
Peter you should have a look at Squeak by example and soon pharo by
example

in short if you had a category with *MyPackage in a class of another
package then
your package MyPackage will contain the extensions.

You can see the extension by clicking on the Monticello browser and
clicking browse.

In fact this is a good practice to check the extensions of a package
before publishing it.

I can show you during the break :)

Stef

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Hej Stef,

I was up quite late last night (=this morning) preparing that huge slice for the WriteStream on: issue, so I overslept this morning, and I have to be at the train station by 12:00 today, so I think I'll stay in my hôtel until then.

But if you can point me to a concrete example, I'm sure I'll understand it when I see it.

--
Cheers,
Peter

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: [ANN]

Stéphane Ducasse
In reply to this post by Michael van der Gulik-2
Yes me too but we should avoid hardcoding class references that core  
everywhere.

Stef

On Sep 3, 2009, at 11:33 PM, Michael van der Gulik wrote:

>
>
> On Fri, Sep 4, 2009 at 3:21 AM, Stéphane Ducasse <[hidden email]
> > wrote:
> - Issue 1144:   Many occurrences of "ReadStream on: aCollection" which
> can be replaced with "aCollection readStream"
>
>
> For what it's worth, I prefer the style of "ReadStream on: xxx". I  
> prefer to choose the stream class rather than let the collection  
> choose it for me.
>
> Gulik.
>
> --
> http://gulik.pbwiki.com/
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: [ANN]

Stéphane Ducasse
In reply to this post by Peter Hugosson-Miller
ok look at the Regex package.
Click browse and you will that regex has class extension in string and  
character.

Stef


> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> Hej Stef,
>
> I was up quite late last night (=this morning) preparing that huge  
> slice for the WriteStream on: issue, so I overslept this morning,  
> and I have to be at the train station by 12:00 today, so I think  
> I'll stay in my hôtel until then.
>
> But if you can point me to a concrete example, I'm sure I'll  
> understand it when I see it.
>
> --
> Cheers,
> Peter
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: [ANN]

Stéphane Ducasse
In reply to this post by Michael Roberts-2
Yes but if we want to make sure that we could plug easily a new stream  
library
we should either use
        virtual classes (quite difficult and major changes at language level)
        or readStream

So readStream gives us a nice solution.

Stef




> I also prefer ReadStream on: since it is explicit about the stream you
> want rather than expecting the collection to know and have the
> protocol. I don't really see the need to rewrite the whole image.
>
> Cheers mike
>
> On Friday, September 4, 2009, Stéphane Ducasse
> <[hidden email]> wrote:
>> Peter you should have a look at Squeak by example and soon pharo by
>> example
>>
>> in short if you had a category with *MyPackage in a class of another
>> package then
>> your package MyPackage will contain the extensions.
>>
>> You can see the extension by clicking on the Monticello browser and
>> clicking browse.
>>
>> In fact this is a good practice to check the extensions of a package
>> before publishing it.
>>
>> I can show you during the break :)
>>
>> Stef
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: [ANN]

Schwab,Wilhelm K
In reply to this post by Michael Roberts-2
I have used #readStream and variants for a long time; I think you will like it if you try it.  The code is cleaner, avoids a set of parentheses at each call, and one can always create variants on it when more control is necessary.

Bill



-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Michael Roberts
Sent: Friday, September 04, 2009 2:45 AM
To: [hidden email]
Subject: Re: [Pharo-project] [ANN]

I also prefer ReadStream on: since it is explicit about the stream you want rather than expecting the collection to know and have the protocol. I don't really see the need to rewrite the whole image.

Cheers mike

On Friday, September 4, 2009, Stéphane Ducasse <[hidden email]> wrote:

> Peter you should have a look at Squeak by example and soon pharo by
> example
>
> in short if you had a category with *MyPackage in a class of another
> package then your package MyPackage will contain the extensions.
>
> You can see the extension by clicking on the Monticello browser and
> clicking browse.
>
> In fact this is a good practice to check the extensions of a package
> before publishing it.
>
> I can show you during the break :)
>
> Stef
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: [ANN]

Schwab,Wilhelm K
In reply to this post by Stéphane Ducasse
 
Stef,

IIRC, Object Arts started promoting name spaces at one point, and (my best guess) ended up finding a very interesting solution using messages.  I believe they call the result an environment, and by asking something for its environment that in turn understands messages to access classes one can do things like

  Smalltalk stef browser show.
  Smalltalk bill browser show.

Where #stef and #bill provide our respective environments, and #browser answers a class.  I'm not sure if  that is at all relevant - free advice is often worth what we pay for it :)

Bill



-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Stéphane Ducasse
Sent: Friday, September 04, 2009 3:05 AM
To: [hidden email]
Subject: Re: [Pharo-project] [ANN]

Yes but if we want to make sure that we could plug easily a new stream library we should either use
        virtual classes (quite difficult and major changes at language level)
        or readStream

So readStream gives us a nice solution.

Stef




> I also prefer ReadStream on: since it is explicit about the stream you
> want rather than expecting the collection to know and have the
> protocol. I don't really see the need to rewrite the whole image.
>
> Cheers mike
>
> On Friday, September 4, 2009, Stéphane Ducasse
> <[hidden email]> wrote:
>> Peter you should have a look at Squeak by example and soon pharo by
>> example
>>
>> in short if you had a category with *MyPackage in a class of another
>> package then your package MyPackage will contain the extensions.
>>
>> You can see the extension by clicking on the Monticello browser and
>> clicking browse.
>>
>> In fact this is a good practice to check the extensions of a package
>> before publishing it.
>>
>> I can show you during the break :)
>>
>> Stef
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
12