July 2011 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [Moose-dev] petitparser tutorial

by Sven Van Caekenberghe

On 12 Jul 2011, at 18:12, Lukas Renggli wrote: >> What do you mean with 'whatever you do, you end up with a broken system' ? >> Any concrete examples ? > > If you do not encode, then you have "unreadable" strings in the image > and operations like #copyFrom:to:, #size, #indexOf:, ... might answer > unexpected or invalid results, because UTF-8 strings are just treated > as byte arrays. Not the way to go IMO. > If you do encode, then you have "readable" strings in the image but > you might run into widestring/encoding problems (check the open issues > on the tracker). I just commented on http://code.google.com/p/pharo/issues/detail?id=2353 which seems to be the most important one. I can't reproduce this (anymore). http://code.google.com/p/pharo/issues/detail?id=830 seems specific to the changelog http://code.google.com/p/pharo/issues/detail?id=2697 is an MC problem The next 2 I reported myself, they are encoding/decoding problems: http://code.google.com/p/pharo/issues/detail?id=3360 http://code.google.com/p/pharo/issues/detail?id=4187 >> Do you have a pointer to Philippe's presentation ? > > http://www.slideshare.net/esug/esug-unicode Thx, reading... Sven

July 12, 2011

Re: [Pharo-users] [Moose-dev] petitparser tutorial

by Lukas Renggli

As Dale writes, changing the encoding of the server now doesn't help. In fact, it will just mess up your model with strings in different encodings. To fix you need to somehow find this Widestring and replace it with an UTF-8 encoded one; or disable the encoding of the server and transform all strings into bytearrays as Strings. The pain with encodings in Pharo is that whatever you do you end up with a broken system in some ways (see philipps presenation last ESUG). If you don't encode in my experience this causes less problems and is more performant. Lukas On Tuesday, 12 July 2011, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi Lukas, > > I now switched to WAKom instead of WAKomEncoded, but the problem still persists. Any ideas? > > Cheers, > Doru > > On 12 Jul 2011, at 13:37, Lukas Renggli wrote: > >> This is a long known problem: >> http://code.google.com/p/pharo/issues/detail?id=2353. For now it can >> only be avoided by not using WideString (i.e. by not using an encoded >> server adapter). >> >> Lukas >> >> On Tuesday, 12 July 2011, giorgio ferraris <giorgio.ferraris(a)gmail.com> wrote: >>> Hi, Tudor, >>> if I use the search facility on the bbok, i get the following: >>> Internal Error >>> Error: subscript is out of bounds: 8218ByteArray(Object)>>errorSubscriptBounds: >>> ByteArray(Object)>>at: >>> WideString(String)>>findSubstring:in:startingAt:matchTable: >>> WideString(String)>>findString:startingAt:caseSensitive: >>> WideString(String)>>includesSubstring:caseSensitive: >>> [] in [] in PRFullTextSearch>>visitStructure: >>> [] in Set(Collection)>>anySatisfy: >>> Set>>do: >>> Set(Collection)>>anySatisfy: >>> [] in PRFullTextSearch>>visitStructure: >>> SortedCollection(OrderedCollection)>>do: >>> MAPriorityContainer(MAContainer)>>do: >>> PRFullTextSearch>>visitStructure: >>> PRFullTextSearch(PRVisitor)>>visitCase: >>> PRFullTextSearch(PRVisitor)>>visitPublication: >>> PRFullTextSearch(PRVisitor)>>visitPortion: >>> BOPortion>>accept: >>> BOPortion(Object)>>acceptDecorated: >>> [] in BOPortion(PRDecorated)>>acceptDecorated: >>> BOPortion(PRDecorated)>>decorationsDo:ownerDo: >>> >>> thanks for the document >>> >>> giorgio ferraris >>> >>> On Mon, Jul 11, 2011 at 2:18 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> Hi, >>> >>> I put together a tutorial for PetitParser in The Moose Book: >>> http://www.themoosebook.org/book/internals/petit-parser/mse >>> >>> The tutorial is meant to work with a Moose image and it is based on the same scenario as I used at the Deep into Smalltalk School: >>> http://www.slideshare.net/girba/petitparser-at-the-deep-into-smalltalk-scho… >>> http://ci.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/arti… >>> >>> >>> Feedback is always appreciated (including the negative one :)). You can either reply by mail, or leave a comment online. >>> >>> Cheers, >>> Doru >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Presenting is storytelling." >>> >>> >>> >>> >>> >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> > > -- > www.tudorgirba.com > > "What is more important: To be happy, or to make happy?" > > > -- Lukas Renggli www.lukas-renggli.ch

July 12, 2011

Re: [Pharo-users] [Moose-dev] petitparser tutorial

by Igor Stasenko

On 12 July 2011 18:12, Lukas Renggli <renggli(a)gmail.com> wrote: >> What do you mean with 'whatever you do, you end up with a broken system' ? >> Any concrete examples ? > > If you do not encode, then you have "unreadable" strings in the image > and operations like #copyFrom:to:, #size, #indexOf:, ... might answer > unexpected or invalid results, because UTF-8 strings are just treated > as byte arrays. > > If you do encode, then you have "readable" strings in the image but > you might run into widestring/encoding problems (check the open issues > on the tracker). > so, what about adding a string subclass UT8String so it can be readable and with correct encoding? :) >> Do you have a pointer to Philippe's presentation ? > > http://www.slideshare.net/esug/esug-unicode > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > > -- Best regards, Igor Stasenko AKA sig.

July 12, 2011

Re: [Pharo-users] [Moose-dev] petitparser tutorial

by Lukas Renggli

> What do you mean with 'whatever you do, you end up with a broken system' ? > Any concrete examples ? If you do not encode, then you have "unreadable" strings in the image and operations like #copyFrom:to:, #size, #indexOf:, ... might answer unexpected or invalid results, because UTF-8 strings are just treated as byte arrays. If you do encode, then you have "readable" strings in the image but you might run into widestring/encoding problems (check the open issues on the tracker). > Do you have a pointer to Philippe's presentation ? http://www.slideshare.net/esug/esug-unicode Lukas -- Lukas Renggli www.lukas-renggli.ch

July 12, 2011

What is the time resolution for TimeStamp?

by Alex Schenkman

Hi List: I've looked at the source code for DateAndTime and TimeStamp but I do not understand it. | t1 t2 | t1 := TimeStamp now. (Delay forMilliseconds: 500 ) wait. t2 := TimeStamp now. (t2 - t1) nanoSeconds. ---> 0 DateAndTime>>clockPrecision says 1 nanosecond. Thanks in advance!

July 12, 2011

Re: [Pharo-users] [Moose-dev] petitparser tutorial

by Lukas Renggli

As Dale writes, changing the encoding of the server now doesn't help. In fact, it will just mess up your model with strings in different encodings. To fix you need to somehow find this Widestring and replace it with an UTF-8 encoded one; or disable the encoding of the server and transform all strings into bytearrays as Strings. The pain with encodings in Pharo is that whatever you do you end up with a broken system in some ways (see philipps presenation last ESUG). If you don't encode in my experience this causes less problems and is more performant. Lukas On Tuesday, 12 July 2011, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi Lukas, > > I now switched to WAKom instead of WAKomEncoded, but the problem still persists. Any ideas? > > Cheers, > Doru > > On 12 Jul 2011, at 13:37, Lukas Renggli wrote: > >> This is a long known problem: >> http://code.google.com/p/pharo/issues/detail?id=2353. For now it can >> only be avoided by not using WideString (i.e. by not using an encoded >> server adapter). >> >> Lukas >> >> On Tuesday, 12 July 2011, giorgio ferraris <giorgio.ferraris(a)gmail.com> wrote: >>> Hi, Tudor, >>> if I use the search facility on the bbok, i get the following: >>> Internal Error >>> Error: subscript is out of bounds: 8218ByteArray(Object)>>errorSubscriptBounds: >>> ByteArray(Object)>>at: >>> WideString(String)>>findSubstring:in:startingAt:matchTable: >>> WideString(String)>>findString:startingAt:caseSensitive: >>> WideString(String)>>includesSubstring:caseSensitive: >>> [] in [] in PRFullTextSearch>>visitStructure: >>> [] in Set(Collection)>>anySatisfy: >>> Set>>do: >>> Set(Collection)>>anySatisfy: >>> [] in PRFullTextSearch>>visitStructure: >>> SortedCollection(OrderedCollection)>>do: >>> MAPriorityContainer(MAContainer)>>do: >>> PRFullTextSearch>>visitStructure: >>> PRFullTextSearch(PRVisitor)>>visitCase: >>> PRFullTextSearch(PRVisitor)>>visitPublication: >>> PRFullTextSearch(PRVisitor)>>visitPortion: >>> BOPortion>>accept: >>> BOPortion(Object)>>acceptDecorated: >>> [] in BOPortion(PRDecorated)>>acceptDecorated: >>> BOPortion(PRDecorated)>>decorationsDo:ownerDo: >>> >>> thanks for the document >>> >>> giorgio ferraris >>> >>> On Mon, Jul 11, 2011 at 2:18 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> Hi, >>> >>> I put together a tutorial for PetitParser in The Moose Book: >>> http://www.themoosebook.org/book/internals/petit-parser/mse >>> >>> The tutorial is meant to work with a Moose image and it is based on the same scenario as I used at the Deep into Smalltalk School: >>> http://www.slideshare.net/girba/petitparser-at-the-deep-into-smalltalk-scho… >>> http://ci.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/arti… >>> >>> >>> Feedback is always appreciated (including the negative one :)). You can either reply by mail, or leave a comment online. >>> >>> Cheers, >>> Doru >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Presenting is storytelling." >>> >>> >>> >>> >>> >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> > > -- > www.tudorgirba.com > > "What is more important: To be happy, or to make happy?" > > > -- Lukas Renggli www.lukas-renggli.ch

July 12, 2011

Re: [Pharo-users] [Moose-dev] petitparser tutorial

by Sven Van Caekenberghe

Lukas, On 12 Jul 2011, at 15:54, Lukas Renggli wrote: > The pain with encodings in Pharo is that whatever you do you end up > with a broken system in some ways (see philipps presenation last > ESUG). If you don't encode in my experience this causes less problems > and is more performant. Of course, not doing encoding/decoding is faster, no question about it. What do you mean with 'whatever you do, you end up with a broken system' ? Any concrete examples ? Do you have a pointer to Philippe's presentation ? Thx, Sven

July 12, 2011

Re: [Pharo-users] [Moose-dev] petitparser tutorial

by Lukas Renggli

As Dale writes, changing the encoding of the server now doesn't help. In fact, it will just mess up your model with strings in different encodings. To fix you need to somehow find this Widestring and replace it with an UTF-8 encoded one; or disable the encoding of the server and transform all strings into bytearrays as Strings. The pain with encodings in Pharo is that whatever you do you end up with a broken system in some ways (see philipps presenation last ESUG). If you don't encode in my experience this causes less problems and is more performant. Lukas On Tuesday, 12 July 2011, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi Lukas, > > I now switched to WAKom instead of WAKomEncoded, but the problem still persists. Any ideas? > > Cheers, > Doru > > On 12 Jul 2011, at 13:37, Lukas Renggli wrote: > >> This is a long known problem: >> http://code.google.com/p/pharo/issues/detail?id=2353. For now it can >> only be avoided by not using WideString (i.e. by not using an encoded >> server adapter). >> >> Lukas >> >> On Tuesday, 12 July 2011, giorgio ferraris <giorgio.ferraris(a)gmail.com> wrote: >>> Hi, Tudor, >>> if I use the search facility on the bbok, i get the following: >>> Internal Error >>> Error: subscript is out of bounds: 8218ByteArray(Object)>>errorSubscriptBounds: >>> ByteArray(Object)>>at: >>> WideString(String)>>findSubstring:in:startingAt:matchTable: >>> WideString(String)>>findString:startingAt:caseSensitive: >>> WideString(String)>>includesSubstring:caseSensitive: >>> [] in [] in PRFullTextSearch>>visitStructure: >>> [] in Set(Collection)>>anySatisfy: >>> Set>>do: >>> Set(Collection)>>anySatisfy: >>> [] in PRFullTextSearch>>visitStructure: >>> SortedCollection(OrderedCollection)>>do: >>> MAPriorityContainer(MAContainer)>>do: >>> PRFullTextSearch>>visitStructure: >>> PRFullTextSearch(PRVisitor)>>visitCase: >>> PRFullTextSearch(PRVisitor)>>visitPublication: >>> PRFullTextSearch(PRVisitor)>>visitPortion: >>> BOPortion>>accept: >>> BOPortion(Object)>>acceptDecorated: >>> [] in BOPortion(PRDecorated)>>acceptDecorated: >>> BOPortion(PRDecorated)>>decorationsDo:ownerDo: >>> >>> thanks for the document >>> >>> giorgio ferraris >>> >>> On Mon, Jul 11, 2011 at 2:18 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> Hi, >>> >>> I put together a tutorial for PetitParser in The Moose Book: >>> http://www.themoosebook.org/book/internals/petit-parser/mse >>> >>> The tutorial is meant to work with a Moose image and it is based on the same scenario as I used at the Deep into Smalltalk School: >>> http://www.slideshare.net/girba/petitparser-at-the-deep-into-smalltalk-scho… >>> http://ci.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/arti… >>> >>> >>> Feedback is always appreciated (including the negative one :)). You can either reply by mail, or leave a comment online. >>> >>> Cheers, >>> Doru >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Presenting is storytelling." >>> >>> >>> >>> >>> >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> > > -- > www.tudorgirba.com > > "What is more important: To be happy, or to make happy?" > > > -- Lukas Renggli www.lukas-renggli.ch

July 12, 2011

Re: [Pharo-users] [Moose-dev] petitparser tutorial

by Dale Henrichs

July 12, 2011

Re: [Pharo-users] [Moose-dev] petitparser tutorial

by Tudor Girba

Hi Lukas, I now switched to WAKom instead of WAKomEncoded, but the problem still persists. Any ideas? Cheers, Doru On 12 Jul 2011, at 13:37, Lukas Renggli wrote: > This is a long known problem: > http://code.google.com/p/pharo/issues/detail?id=2353. For now it can > only be avoided by not using WideString (i.e. by not using an encoded > server adapter). > > Lukas > > On Tuesday, 12 July 2011, giorgio ferraris <giorgio.ferraris(a)gmail.com> wrote: >> Hi, Tudor, >> if I use the search facility on the bbok, i get the following: >> Internal Error >> Error: subscript is out of bounds: 8218ByteArray(Object)>>errorSubscriptBounds: >> ByteArray(Object)>>at: >> WideString(String)>>findSubstring:in:startingAt:matchTable: >> WideString(String)>>findString:startingAt:caseSensitive: >> WideString(String)>>includesSubstring:caseSensitive: >> [] in [] in PRFullTextSearch>>visitStructure: >> [] in Set(Collection)>>anySatisfy: >> Set>>do: >> Set(Collection)>>anySatisfy: >> [] in PRFullTextSearch>>visitStructure: >> SortedCollection(OrderedCollection)>>do: >> MAPriorityContainer(MAContainer)>>do: >> PRFullTextSearch>>visitStructure: >> PRFullTextSearch(PRVisitor)>>visitCase: >> PRFullTextSearch(PRVisitor)>>visitPublication: >> PRFullTextSearch(PRVisitor)>>visitPortion: >> BOPortion>>accept: >> BOPortion(Object)>>acceptDecorated: >> [] in BOPortion(PRDecorated)>>acceptDecorated: >> BOPortion(PRDecorated)>>decorationsDo:ownerDo: >> >> thanks for the document >> >> giorgio ferraris >> >> On Mon, Jul 11, 2011 at 2:18 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> I put together a tutorial for PetitParser in The Moose Book: >> http://www.themoosebook.org/book/internals/petit-parser/mse >> >> The tutorial is meant to work with a Moose image and it is based on the same scenario as I used at the Deep into Smalltalk School: >> http://www.slideshare.net/girba/petitparser-at-the-deep-into-smalltalk-scho… >> http://ci.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/arti… >> >> >> Feedback is always appreciated (including the negative one :)). You can either reply by mail, or leave a comment online. >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com >> >> "Presenting is storytelling." >> >> >> >> >> > > -- > Lukas Renggli > www.lukas-renggli.ch > -- www.tudorgirba.com "What is more important: To be happy, or to make happy?"

July 12, 2011