April 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] ZnCookie>>#fromString: uses subStrings:

by Yuriy Tymchuk

Well, QualityAssistant cannot be loaded into Pharo5 without warnings. I donât know how many people use it, but it can bother them. Uko > On 30 Apr 2015, at 11:29, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Zinc was already updated in #bleedingEdge. > > Does this block you ? > > If so, I have to create a new #stable version and ask for it to be integrated in Pharo 5.0 > >> On 30 Apr 2015, at 11:15, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >> And #subStrings: were deprecated in favor of #substrings: >> >> Can someone update Zinc? >> >> Thanks! >> Uko >> > >

April 30, 2015

Re: [Pharo-dev] Differences between TextConverters and ZnEncoders

by Norbert Hartl

If yours is better there shouldn't be much of a reason to keep the bad one, right? I'd just suggest that pharo does not depend on zinc classes but the encoder moves to pharo with a different name. Norbert > Am 30.04.2015 um 11:42 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > >> On 30 Apr 2015, at 11:13, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >> >> Hi! >> >> I'm struggling with the TextConverter's API in Pharo :). >> >> I wanted to test the converters in Pharo, and I found the method #convertFromSystemString: that should (from its name) convert a Pharo String into an encoded version of it. >> >> (UTF8TextConverter default convertFromSystemString: 'Ã¡'). >> >> Funny thing, it does not do that. It does the opposite: it tries to convert an encoded string to a pharo string. And so it fails. Of course, its symmetrical version does what I want and behaves as the ZnUTF8Encoder :) >> >> (UTF8TextConverter default convertToSystemString: 'Ã¡') asByteArray >> "#[195 161]" >> >> ZnUTF8Encoder new encodeString: 'Ã¡' "#[195 161]" >> >> Question: >> - does the convertTo/From methods makes sense to you or It's just me that sees them inverted? >> - does it make sense to have the two versions of converters? Zn and the TextConverters do the same in my opinion (or maybe I'm confused :) ) >> >> Guille > > I am biased, but the Zn converters are better. Why ? Because they work between String <-> Bytes as a text encoder/decoder should. They also have a number of extra features (counting the number of encoded bytes, being able to move backwards on input, being able to be very strict), are faster and have a clearer implementation. Furthermore, they are more correct and implement more encodings. > > There is also good documentation http://stfx.eu/EnterprisePharo/Zinc-Encoding-Meta/ > > ZnCharacter[Read|Write]Stream are also very instructive, compare them to MultiByteStream. > > Should we throw the other one out ? Probably. But it is the same problems as with Xtreams: the API is different and adding a compatibility layer would defeat the purpose. So I don't know. > > Sven > > >

April 30, 2015

Re: [Pharo-dev] Differences between TextConverters and ZnEncoders

by Sven Van Caekenberghe

> On 30 Apr 2015, at 11:13, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Hi! > > I'm struggling with the TextConverter's API in Pharo :). > > I wanted to test the converters in Pharo, and I found the method #convertFromSystemString: that should (from its name) convert a Pharo String into an encoded version of it. > > (UTF8TextConverter default convertFromSystemString: 'Ã¡'). > > Funny thing, it does not do that. It does the opposite: it tries to convert an encoded string to a pharo string. And so it fails. Of course, its symmetrical version does what I want and behaves as the ZnUTF8Encoder :) > > (UTF8TextConverter default convertToSystemString: 'Ã¡') asByteArray > "#[195 161]" > > ZnUTF8Encoder new encodeString: 'Ã¡' "#[195 161]" > > Question: > - does the convertTo/From methods makes sense to you or It's just me that sees them inverted? > - does it make sense to have the two versions of converters? Zn and the TextConverters do the same in my opinion (or maybe I'm confused :) ) > > Guille I am biased, but the Zn converters are better. Why ? Because they work between String <-> Bytes as a text encoder/decoder should. They also have a number of extra features (counting the number of encoded bytes, being able to move backwards on input, being able to be very strict), are faster and have a clearer implementation. Furthermore, they are more correct and implement more encodings. There is also good documentation http://stfx.eu/EnterprisePharo/Zinc-Encoding-Meta/ ZnCharacter[Read|Write]Stream are also very instructive, compare them to MultiByteStream. Should we throw the other one out ? Probably. But it is the same problems as with Xtreams: the API is different and adding a compatibility layer would defeat the purpose. So I don't know. Sven

April 30, 2015

Re: [Pharo-dev] build pharo vm on windows (old mingw package)

by Esteban Lorenzano

arenât you able to install an older version of gcc in your newer version of mingw? I do not have time right now to update the build into a new compiler, sorry (also, that is not always trivial/desired, he) Esteban > On 30 Apr 2015, at 08:38, Nicolai Hess <nicolaihess(a)web.de> wrote: > > I managed to trash my mingw build environment > -> uninstalled /removed mingw/mingsys > -> reinstall from current mingw-installer > -> bad idea > > I can build a pharo windows vm but it immediately crashes on startup. I suspect > some changes between gcc 4.6 (old environment) gcc 4.8 (new environment). > (I think there are some changes related to file globbing (I managed to get > the vm somehow working to not crash on startup but on shutdown instead - with > _CRT_glob = 0. And gcc-4.8 uses dfferent (dwarf vs. sjlj ) exception handling, don't know if this is > related). > > I tried to find a ming-installer for the old version but could not find anything and > I tried to manually setup a ming installation from the old packages (dozen of packages > for mingw / core-utils / bintutils /msys from different places (no fun)). > > 1) did anyone get a windows vm from mingws current version (with gcc 4.8) working? > > 2) can someone package/zip and upload an old mingw installation (maybe that one that > is used on the build server? > > > regards > nicolai

April 30, 2015

Re: [Pharo-dev] ZnCookie>>#fromString: uses subStrings:

by Sven Van Caekenberghe

Zinc was already updated in #bleedingEdge. Does this block you ? If so, I have to create a new #stable version and ask for it to be integrated in Pharo 5.0 > On 30 Apr 2015, at 11:15, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > And #subStrings: were deprecated in favor of #substrings: > > Can someone update Zinc? > > Thanks! > Uko >

April 30, 2015

Re: [Pharo-dev] Strange bug with interruption and fonts

by Norbert Hartl

> Am 30.04.2015 um 10:40 schrieb stepharo <stepharo(a)free.fr>: > > Hi > > I was coding with my son some little programs and we did an endless loop. > I tried to break the execution. > And afetr some efforts I succeeded to get back the system but I cannot open the browser, the debugger, playground.... > because of fonts so the only thing I can do is a screenshot. :( > I cannot try with the default workspace. > > I got the bug in the past already > I get this, too, from time to time. The only way to "cure" it is to close the image and reopen. Norbert

April 30, 2015

Re: [Pharo-dev] Why selecting and printing a variable in the debuger does not work?

by Nicolai Hess

2015-04-30 11:04 GMT+02:00 stepharo <stepharo(a)free.fr>: > I get now > Error while printing (self namedTempAt: 1) > > Le 30/4/15 11:04, stepharo a Ã©crit : > > Hi >> >> is it a know bug? >> Why selecting and printing a variable in the debuger does not work? >> >> Stef >> >> >> >> > Maybe the fix for 14606 <https://pharo.fogbugz.com/default.asp?14606> Can't see some variables values while debugging closure was incomplete and only works for variables in the context inspector but not in the debugger text pane? Or it depends on the code. Maybe the object you try to print is incomplete initialized?

April 30, 2015

ZnCookie>>#fromString: uses subStrings:

by Yuriy Tymchuk

And #subStrings: were deprecated in favor of #substrings: Can someone update Zinc? Thanks! Uko

April 30, 2015

Differences between TextConverters and ZnEncoders

by Guillermo Polito

Hi! I'm struggling with the TextConverter's API in Pharo :). I wanted to test the converters in Pharo, and I found the method #convertFromSystemString: that should (from its name) convert a Pharo String into an encoded version of it. (UTF8TextConverter default convertFromSystemString: 'Ã¡'). Funny thing, it does not do that. It does the opposite: it tries to convert an encoded string to a pharo string. And so it fails. Of course, its symmetrical version does what I want and behaves as the ZnUTF8Encoder :) (UTF8TextConverter default convertToSystemString: 'Ã¡') asByteArray "#[195 161]" ZnUTF8Encoder new encodeString: 'Ã¡' "#[195 161]" Question: - does the convertTo/From methods makes sense to you or It's just me that sees them inverted? - does it make sense to have the two versions of converters? Zn and the TextConverters do the same in my opinion (or maybe I'm confused :) ) Guille

April 30, 2015

Re: [Pharo-dev] Why selecting and printing a variable in the debuger does not work?

by stepharo

I get now Error while printing (self namedTempAt: 1) Le 30/4/15 11:04, stepharo a Ã©crit : > Hi > > is it a know bug? > Why selecting and printing a variable in the debuger does not work? > > Stef > > >

April 30, 2015