- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Latest Zinc in Pharo 1.3 with MetacelloConfiguration

by Sven Van Caekenberghe

FranÃ§ois, On 12 Dec 2011, at 21:46, Francois Stephany wrote: > Dag Sven, > >> It would be great if you could update both to the latest versions of all packages. > > I've updated the configuration to all the latest packages except for Gemstone. > > Wehn Running the 190 tests I get one failure: > > ZnClientTests>>testIfFailNonExistingHost > > > Let me now if I did something wrong ;) Please do also copy it to the main http://www.squeaksource.com/ZincHTTPComponents repository. I know having 2 is confusing, but that is how most projects seem to do it. I don't understand why you would try to get Zinc-Patch-HTTPSocket from this other repository (they are identical BTW). The failing test puzzle me, can you maybe debug it and tell me what you see ? Maybe we should also let Paul DeBruicker know what you did, if he's not reading this. Thanks again, Sven

Dec. 14, 2011

Re: [Pharo-project] ZnUrl vs furl

by StÃ©phane Ducasse

On Dec 14, 2011, at 2:09 PM, Sven Van Caekenberghe wrote: > > On 14 Dec 2011, at 14:00, Sven Van Caekenberghe wrote: > >> Now it reads like this: > > Actually with the correct quotes (I did a ZnUrl comment Print It ;-) > BTW, I already did add the examples as unit tests, executable code is even better than dead comments. Yes I do not despair to have pragma <forDoc> in unit tests for that. Stef > > > I am ZnUrl, an implementation of an interpreted HTTP(S) URL/URI. > Contrary to other implementations, this one is specific for HTTP(S). > > I consist of the following parts: > - scheme - either #http, #https or nil > - host - hostname string or nil > - port - port integer or nil > - segments - collection of path segments, ends with #/ for directories > - query - query dictionary or nil > - fragment - fragment string or nil > > The syntax of my external representation informally looks like this > > scheme://host:port/segments?query#fragment > > I am most often created by parsing my external representation using either my #fromString: class method or by sending the #asZnUrl convenience method to a String. Using #asZnUrl helps in accepting both Strings and ZnUrls arguments. > > ZnUrl fromString: 'http://www.google.com/search?q=Smalltalk'. > > I can also be constucted programmatically. > > ZnUrl new > scheme: #https; > host: 'encrypted.google.com'; > addPathSegment: 'search'; > queryAt: 'q' put: 'Smalltalk'; > yourself. > > My components can be manipulated destructively. Here is an example: > > ('http://www.google.com/?one=1&two=2' asZnUrl) > queryAt: 'three' put: '3'; > queryRemoveKey: 'one'; > yourself. > > Some characters of parts of a URL are illegal because they would interfere with the syntax and further processing and thus have to be encoded. The methods in accessing protocols do not do any encoding, those in parsing and printing do. Here is an example: > > ('http://www.google.com' asZnUrl) > addPathSegment: 'some encoding here'; > queryAt: 'and some encoding' put: 'here, too'; > yourself > > My parser is somewhat forgiving and accepts some unencoded URLs as well, like most browsers would. > > 'http://www.example.com:8888/a path?q=a, b, c' asZnUrl. > > I can parse in the context of a default scheme, like a browser would do. > > ZnUrl fromString: 'www.example.com' defaultScheme: #http > > Given a scheme, I know its default port, try #portOrDefault. > > A path defaults to what is commonly referred to as slash, test with #isSlash. Paths are most often (but don't have to be) interpreted as filesystem paths. To support this, I have #isFile and #isDirectory tests and #file and #directory accessors. > > I have some support to handle one URL in the context of another one, this is also known as a relative URL in the context of an absolute URL. Refer to #isAbsolute, #isRelative and #inContextOf: > > '/folder/file.txt' asZnUrl inContextOf: ('http://fileserver.example.net:4400' asZnUrl). > > Sometimes, the combination of my host and port are referred to as authority, see #authority. > > URL/URI/URN (Uniform/Universal Resource Locator/Identifier/Name) are closely related and can be and are used as synonyms is many contexts. Refer to http://en.wikipedia.org/wiki/Url for more information. > > Part of Zinc HTTP Components.

Dec. 14, 2011

Re: [Pharo-project] ZnUrl vs furl

by StÃ©phane Ducasse

On Dec 14, 2011, at 2:00 PM, Sven Van Caekenberghe wrote: > > On 13 Dec 2011, at 22:42, StÃ©phane Ducasse wrote: > >> Excellent now can you open an issue and provide add these examples in the ZnUrl class comment? > > You are a slave driver ;-) Yes I like that. whipping the crack :) Stef > > ==================== Summary ==================== > > Name: Zinc-HTTP-SvenVanCaekenberghe.229 > Author: SvenVanCaekenberghe > Time: 14 December 2011, 1:45:28 pm > UUID: b239edd4-c432-4139-a71a-d27618beef91 > Ancestors: Zinc-HTTP-SvenVanCaekenberghe.228 > > expanded the ZnUrl class comment > > ================================================= > > > Now it reads like this: > > > I am ZnUrl, an implementation of an interpreted HTTP(S) URL/URI. > Contrary to other implementations, this one is specific for HTTP(S). > > I consist of the following parts: > - scheme - either #http, #https or nil > - host - hostname string or nil > - port - port integer or nil > - segments - collection of path segments, ends with #/ for directories > - query - query dictionary or nil > - fragment - fragment string or nil > > The syntax of my external representation informally looks like this > > scheme://host:port/segments?query#fragment > > I am most often created by parsing my external representation using either my #fromString: class method or by sending the #asZnUrl convenience method to a String. Using #asZnUrl helps in accepting both Strings and ZnUrls arguments. > > ZnUrl fromString: ''http://www.google.com/search?q=Smalltalk''. > > I can also be constucted programmatically. > > ZnUrl new > scheme: #https; > host: ''encrypted.google.com''; > addPathSegment: ''search''; > queryAt: ''q'' put: ''Smalltalk''; > yourself. > > My components can be manipulated destructively. Here is an example: > > (''http://www.google.com/?one=1&two=2'' asZnUrl) > queryAt: ''three'' put: ''3''; > queryRemoveKey: ''one''; > yourself. > > Some characters of parts of a URL are illegal because they would interfere with the syntax and further processing and thus have to be encoded. The methods in accessing protocols do not do any encoding, those in parsing and printing do. Here is an example: > > (''http://www.google.com'' asZnUrl) > addPathSegment: ''some encoding here''; > queryAt: ''and some encoding'' put: ''here, too''; > yourself > > My parser is somewhat forgiving and accepts some unencoded URLs as well, like most browsers would. > > ''http://www.example.com:8888/a path?q=a, b, c'' asZnUrl. > > I can parse in the context of a default scheme, like a browser would do. > > ZnUrl fromString: ''www.example.com'' defaultScheme: #http > > Given a scheme, I know its default port, try #portOrDefault. > > A path defaults to what is commonly referred to as slash, test with #isSlash. Paths are most often (but don''t have to be) interpreted as filesystem paths. To support this, I have #isFile and #isDirectory tests and #file and #directory accessors. > > I have some support to handle one URL in the context of another one, this is also known as a relative URL in the context of an absolute URL. Refer to #isAbsolute, #isRelative and #inContextOf: > > ''/folder/file.txt'' asZnUrl inContextOf: (''http://fileserver.example.net:4400'' asZnUrl). > > Sometimes, the combination of my host and port are referred to as authority, see #authority. > > URL/URI/URN (Uniform/Universal Resource Locator/Identifier/Name) are closely related and can be and are used as synonyms is many contexts. Refer to http://en.wikipedia.org/wiki/Url for more information. > > Part of Zinc HTTP Components. > >

Dec. 14, 2011

Re: [Pharo-project] ZnUrl vs furl

by Sven Van Caekenberghe

On 14 Dec 2011, at 14:00, Sven Van Caekenberghe wrote: > Now it reads like this: Actually with the correct quotes (I did a ZnUrl comment Print It ;-) BTW, I already did add the examples as unit tests, executable code is even better than dead comments. I am ZnUrl, an implementation of an interpreted HTTP(S) URL/URI. Contrary to other implementations, this one is specific for HTTP(S). I consist of the following parts: - scheme - either #http, #https or nil - host - hostname string or nil - port - port integer or nil - segments - collection of path segments, ends with #/ for directories - query - query dictionary or nil - fragment - fragment string or nil The syntax of my external representation informally looks like this scheme://host:port/segments?query#fragment I am most often created by parsing my external representation using either my #fromString: class method or by sending the #asZnUrl convenience method to a String. Using #asZnUrl helps in accepting both Strings and ZnUrls arguments. ZnUrl fromString: 'http://www.google.com/search?q=Smalltalk'. I can also be constucted programmatically. ZnUrl new scheme: #https; host: 'encrypted.google.com'; addPathSegment: 'search'; queryAt: 'q' put: 'Smalltalk'; yourself. My components can be manipulated destructively. Here is an example: ('http://www.google.com/?one=1&two=2' asZnUrl) queryAt: 'three' put: '3'; queryRemoveKey: 'one'; yourself. Some characters of parts of a URL are illegal because they would interfere with the syntax and further processing and thus have to be encoded. The methods in accessing protocols do not do any encoding, those in parsing and printing do. Here is an example: ('http://www.google.com' asZnUrl) addPathSegment: 'some encoding here'; queryAt: 'and some encoding' put: 'here, too'; yourself My parser is somewhat forgiving and accepts some unencoded URLs as well, like most browsers would. 'http://www.example.com:8888/a path?q=a, b, c' asZnUrl. I can parse in the context of a default scheme, like a browser would do. ZnUrl fromString: 'www.example.com' defaultScheme: #http Given a scheme, I know its default port, try #portOrDefault. A path defaults to what is commonly referred to as slash, test with #isSlash. Paths are most often (but don't have to be) interpreted as filesystem paths. To support this, I have #isFile and #isDirectory tests and #file and #directory accessors. I have some support to handle one URL in the context of another one, this is also known as a relative URL in the context of an absolute URL. Refer to #isAbsolute, #isRelative and #inContextOf: '/folder/file.txt' asZnUrl inContextOf: ('http://fileserver.example.net:4400' asZnUrl). Sometimes, the combination of my host and port are referred to as authority, see #authority. URL/URI/URN (Uniform/Universal Resource Locator/Identifier/Name) are closely related and can be and are used as synonyms is many contexts. Refer to http://en.wikipedia.org/wiki/Url for more information. Part of Zinc HTTP Components.

Dec. 14, 2011

Re: [Pharo-project] ZnUrl vs furl

by Sven Van Caekenberghe

On 13 Dec 2011, at 22:42, StÃ©phane Ducasse wrote: > Excellent now can you open an issue and provide add these examples in the ZnUrl class comment? You are a slave driver ;-) ==================== Summary ==================== Name: Zinc-HTTP-SvenVanCaekenberghe.229 Author: SvenVanCaekenberghe Time: 14 December 2011, 1:45:28 pm UUID: b239edd4-c432-4139-a71a-d27618beef91 Ancestors: Zinc-HTTP-SvenVanCaekenberghe.228 expanded the ZnUrl class comment ================================================= Now it reads like this: I am ZnUrl, an implementation of an interpreted HTTP(S) URL/URI. Contrary to other implementations, this one is specific for HTTP(S). I consist of the following parts: - scheme - either #http, #https or nil - host - hostname string or nil - port - port integer or nil - segments - collection of path segments, ends with #/ for directories - query - query dictionary or nil - fragment - fragment string or nil The syntax of my external representation informally looks like this scheme://host:port/segments?query#fragment I am most often created by parsing my external representation using either my #fromString: class method or by sending the #asZnUrl convenience method to a String. Using #asZnUrl helps in accepting both Strings and ZnUrls arguments. ZnUrl fromString: ''http://www.google.com/search?q=Smalltalk''. I can also be constucted programmatically. ZnUrl new scheme: #https; host: ''encrypted.google.com''; addPathSegment: ''search''; queryAt: ''q'' put: ''Smalltalk''; yourself. My components can be manipulated destructively. Here is an example: (''http://www.google.com/?one=1&two=2'' asZnUrl) queryAt: ''three'' put: ''3''; queryRemoveKey: ''one''; yourself. Some characters of parts of a URL are illegal because they would interfere with the syntax and further processing and thus have to be encoded. The methods in accessing protocols do not do any encoding, those in parsing and printing do. Here is an example: (''http://www.google.com'' asZnUrl) addPathSegment: ''some encoding here''; queryAt: ''and some encoding'' put: ''here, too''; yourself My parser is somewhat forgiving and accepts some unencoded URLs as well, like most browsers would. ''http://www.example.com:8888/a path?q=a, b, c'' asZnUrl. I can parse in the context of a default scheme, like a browser would do. ZnUrl fromString: ''www.example.com'' defaultScheme: #http Given a scheme, I know its default port, try #portOrDefault. A path defaults to what is commonly referred to as slash, test with #isSlash. Paths are most often (but don''t have to be) interpreted as filesystem paths. To support this, I have #isFile and #isDirectory tests and #file and #directory accessors. I have some support to handle one URL in the context of another one, this is also known as a relative URL in the context of an absolute URL. Refer to #isAbsolute, #isRelative and #inContextOf: ''/folder/file.txt'' asZnUrl inContextOf: (''http://fileserver.example.net:4400'' asZnUrl). Sometimes, the combination of my host and port are referred to as authority, see #authority. URL/URI/URN (Uniform/Universal Resource Locator/Identifier/Name) are closely related and can be and are used as synonyms is many contexts. Refer to http://en.wikipedia.org/wiki/Url for more information. Part of Zinc HTTP Components.

Dec. 14, 2011

Re: [Pharo-project] [COTDC] 96 - GZipWriteStream

by Igor Stasenko

On 14 December 2011 08:55, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I do not believe in that crap :) > > A class comment can also explain the public interface, the hooks for subclasses, the collaborators > > So all the classes deserve that care. > the thing is, that given stream having no new protocol comparing to superclass. > Stef > >> i think the name is self-explanatory. there's nothing to say about it >> without being Cpt Obvious :) >> >> On 14 December 2011 05:19, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >>> No love for the Compression package? >>> >>> -- >>> View this message in context: http://forum.world.st/COTDC-96-GZipWriteStream-tp4188550p4193552.html >>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > -- Best regards, Igor Stasenko.

Dec. 14, 2011

Re: [Pharo-project] Startup Preferences

by Benjamin

On Dec 14, 2011, at 1:09 PM, Stefan Marr wrote: > Hi Benjamin: > > On 13 Dec 2011, at 11:37, Benjamin wrote: > >> New version: >> >> Gofer new >> squeaksource: 'StartupPreferences'; >> package: 'StartupPreferences'; >> load. >> >> Ben > > Works, great, thanks. > One detail: could you make sure that the files are written out with the standard line ending of the platform? > This is usually a big pain with Smalltalk, the infrastructure is there, but usually not used. And now I end up with config files that are not easily editable in for instance vim. I was wondering why nano opened the files in a strange way ;) I will change that right now ;) Thanks, Ben > Thanks > Stefan > > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > >

Dec. 14, 2011

[Pharo-project] Out of the box primitives for bit in ObjectHeader?

by Mariano Martinez Peck

Hi guys. As you may notice, I always try to push in the direction of a VM where we can have both things: a) a really cooler super fast VM for production super critical applications and b) the most-flexible-possible VM for doing reasearh and experiment. Now I was thinking the following: we have one free bit in the ObjectHeader. Let's say you are experimenting with something and you would like to tag objects, such as, "traversed", "processes", "isProxy", etc. To do that small experiment you need to modify the VM, adapt the bit, code the primitives, build the VM, put the smalltalk side part etc etc. So I was thinking why not providing such small functionality out of the box? the idea would be not to give semantics to the bit since each user will do that. So we just provide the VM with 2 primtives, one to get the value (#getBitValue) and one to set it (#setBitTo:). Choose the names you want. Then we do not integrate nothing in our images that use such bit, there won't be colisions. Then each guy who wants to experiments with that, can use the primitives and do what he wants. Some people is doing something with its bit: Jean Batiptse is doing XXX, I am doing YYY, etc. Either in his work or mine, there are much more changes that just that bit, so in anyway, I will end up needing my own VM. Finally, I could help in providing the code if it is needed. So, what do you think? -- Mariano http://marianopeck.wordpress.com

Dec. 14, 2011

Re: [Pharo-project] Startup Preferences

by Stefan Marr

Hi Benjamin: On 13 Dec 2011, at 11:37, Benjamin wrote: > New version: > > Gofer new > squeaksource: 'StartupPreferences'; > package: 'StartupPreferences'; > load. > > Ben Works, great, thanks. One detail: could you make sure that the files are written out with the standard line ending of the platform? This is usually a big pain with Smalltalk, the infrastructure is there, but usually not used. And now I end up with config files that are not easily editable in for instance vim. Thanks Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

Dec. 14, 2011

Re: [Pharo-project] hasPoolVarNamed: semantics :(

by Mariano Martinez Peck

On Wed, Dec 14, 2011 at 2:34 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > Stephane, remember we changed a name lookup for classes not long ago. > IIRC we changed the #bindingOf: > So, i think that #sharedPools should answer a list of all pools of all > classes in inheritance chain, which can be implemented like: > > sharedPools > > ^ superclass ifNil: [ self localSharedPools ] ifNotNil: [ self > localSharedPools , superclass sharedPools ] > mmmmmmm if you follow must of the existing methods similar to this one, I would understand that #sharedPools answers ONLY the localSharedPools and I would undertand there is a message #allSharedPools which answer what you are saying. > > note, that order (self localSharedPools , superclass sharedPools) are > important, because pool in a subclass > can shadow a pool variable defined in superclass. > > -- > Best regards, > Igor Stasenko. > > -- Mariano http://marianopeck.wordpress.com

Dec. 14, 2011