- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] funny TIOBE

by Torsten Bergmann

> Von: Pharo4Stef > > On 28 Mar 2014, at 22:00, Sean P. DeNigris wrote: > > > Pavel Krivanek-3 wrote > >> after a very long time I checked the TIOBE index and Smalltalk is not > >> listed there at all... :-) > > > > Maybe we died and don't know it... must be heaven, not hot enough for the > > other place ;) > > :) > <quote_from_tiobe_FAQ> Q: I would like to have the complete data set of the TIOBE index. Is this possible? A: We spent a lot of effort to obtain all the data and keep the TIOBE index up to date. In order to compensate a bit for this, we ask a fee of 5,000 US$ for the complete data set. </quote_from_tiobe_FAQ> I'm sure you paid them more than 5000 bucks to remove it from the data set so Smalltalk can still be kept as a secret... And I guess this is already known: http://astares.blogspot.de/2006/07/stupid-metrics.html Bye T.

March 28, 2014

Re: [Pharo-dev] VistaCursors are killing my LinuxVM (beCursor primitive failing)

by Nicolai Hess

Yes we have this issue: 12960 <https://pharo.fogbugz.com/default.asp?12960> Primitive 101 (Cursor beCursor) fails on Ubuntu we just need someone who can edit the pharo vm build config. 2014-03-28 18:52 GMT+01:00 phil(a)highoctane.be <phil(a)highoctane.be>: > I moved a windows image with VistaCursors to Linux and the beCursor > primitive failed, leading to a white screen opening. > > Maybe this is because the cursors are bigger than the 16x16 form. > > I saw discussions of this being fixed in Squeak. Are we having this issue > in Pharo? > > Phil >

March 28, 2014

Re: [Pharo-dev] funny TIOBE

by Stephan Eggermont

Sean wrote: >Maybe we died and don't know it... must be heaven, not hot enough for the other place ;) Well, I donât know. We keep on fixing bugs and donât get any closer to release :) Stephan

March 28, 2014

Re: [Pharo-dev] Every class should redefine printOn:

by Pharo4Stef

On 28 Mar 2014, at 22:08, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I am all for that, but I don't think you can make it that strict, what if there are no instance variables ? ok :) a smart rule > I like custom #printOn:'s especially for debugging. > > On 28 Mar 2014, at 21:45, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > >> Hi guys >> >> Iâm trying to understand freeType and when I debug I get aBlah aFoo and this is frankly annoying >> because Iâm trying to learn the implementation and it does not help me at all. >> >> I hate the classes that only their implementors understand. >> In Pharo 4.0 I will put a strict rule: >> - no class will be integrated if they do not redefine printOn: >> - I will set a general rules to check printOn: methods. >> >> printOn: methods are the first debugging information. >> >> Stef > >

March 28, 2014

Re: [Pharo-dev] Every class should redefine printOn:

by Sven Van Caekenberghe

I am all for that, but I don't think you can make it that strict, what if there are no instance variables ? I like custom #printOn:'s especially for debugging. On 28 Mar 2014, at 21:45, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > Hi guys > > Iâm trying to understand freeType and when I debug I get aBlah aFoo and this is frankly annoying > because Iâm trying to learn the implementation and it does not help me at all. > > I hate the classes that only their implementors understand. > In Pharo 4.0 I will put a strict rule: > - no class will be integrated if they do not redefine printOn: > - I will set a general rules to check printOn: methods. > > printOn: methods are the first debugging information. > > Stef

March 28, 2014

Re: [Pharo-dev] funny TIOBE

by Pharo4Stef

On 28 Mar 2014, at 22:00, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Pavel Krivanek-3 wrote >> after a very long time I checked the TIOBE index and Smalltalk is not >> listed there at all... :-) > > Maybe we died and don't know it... must be heaven, not hot enough for the > other place ;) :) > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/funny-TIOBE-tp4751510p4751522.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

March 28, 2014

Re: [Pharo-dev] funny TIOBE

by Sean P. DeNigris

Pavel Krivanek-3 wrote > after a very long time I checked the TIOBE index and Smalltalk is not > listed there at all... :-) Maybe we died and don't know it... must be heaven, not hot enough for the other place ;) ----- Cheers, Sean -- View this message in context: http://forum.world.st/funny-TIOBE-tp4751510p4751522.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 28, 2014

Re: [Pharo-dev] Capturing stdout

by Sean P. DeNigris

Emilio Oca-3 wrote > I managed to do that in Windows using... ProcessWrapper... As it's for a core test, I need to find a way to do it without loading additional libraries. I could pipe the output to a tmp file if there's nothing... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Capturing-stdout-tp4751320p4751521.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 28, 2014

Every class should redefine printOn:

by Pharo4Stef

Hi guys Iâm trying to understand freeType and when I debug I get aBlah aFoo and this is frankly annoying because Iâm trying to learn the implementation and it does not help me at all. I hate the classes that only their implementors understand. In Pharo 4.0 I will put a strict rule: - no class will be integrated if they do not redefine printOn: - I will set a general rules to check printOn: methods. printOn: methods are the first debugging information. Stef

March 28, 2014

Re: [Pharo-dev] [Moose-dev] Re: Re: Re: Fwd: Font problem is still there

by Pharo4Stef

thanks Igor. Iâm trying to look at the font reloading bug. On 28 Mar 2014, at 17:19, Igor Stasenko <siguctua(a)gmail.com> wrote: > https://pharo.fogbugz.com/f/cases/13150/Different-memory-alignment-on-diffe… > > > On 28 March 2014 16:42, Igor Stasenko <siguctua(a)gmail.com> wrote: > so, the quick and dirty fix is to put: > > CairoGlyph class>>byteAlignment > > NativeBoost platformId = NativeBoostConstants win32PlatformId ifTrue: [ ^ 8 ]. > ^ super byteAlignment > > and then: > > CairoGlyph rebuildFieldAccessors > CairoGlyphsArray initialize > > (note you must run this snippet each time your image changes platform).. > > and i need more time to fix it for real, because it is NB issue, to automatically recalculate the structs size > if it changes platform.. (which also means you cannot store instances of struct in image which survive the session) > ... damn.. that's going to be complicated. > > --- > > > > On 28 March 2014 16:27, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > > On 28 March 2014 16:01, Igor Stasenko <siguctua(a)gmail.com> wrote: > > Ookkayy.. > so, current status: > > - finally we got an agreement that big red square because of font loading issues and font rendering artifacts is two separate issues. > Thanks! > - i am not going to address font-loading issue here and now.. (because we spent time on it earlier today with Stef already and you should have the report on it in separate mail). > > - we seem to be agreed that it is best to use same (up-to-date version) of software when reporting issues to work on them. Thanks again. :) > > - while on linux and mac things seem to be working fine, i can confirm that there is rendering artifacts (same as reported by Vincent) on Windows. > > so i going to explore what causing this problem.. > > ... and found the cause: > > On windows, for unknown reason, the structure (cairo_glyph_t) uses different memory space alignment than on mac and linux > > fieldsDesc > ^ #( > ulong index; > double x; > double y; > ) > > on mac and linux , the size of this structure in memory = 4 + 8 + 8 = 20 bytes, > on windows, however, due to 8-byte alignment, it is 4 + 8 + 8 + (4 alignment) bytes... > > this causing the effect that if you copy array of glyphs in memory, > it does not copying whole array by slightly less (because it uses wrong struct size which is smaller than it is).. > and because of that, you got weird artefacts at the tail of string, replaced by misplaced/invalid characters etc.. > because it is basically read from uninitialized part of memory with random data. > > i going to fix structure alignment for windows from default 4 bytes to 8 bytes.. > but this is not very good news.. because this affecting many things... (as you can imagine, not only cairo/athens working with external structures, which need to be properly aligned). > > -- > Best regards, > Igor Stasenko. > > > > -- > Best regards, > Igor Stasenko. > > > > -- > Best regards, > Igor Stasenko.

March 28, 2014