July 2016 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60137 Home: https://github.com/pharo-project/pharo-core

July 6, 2016

[pharo-project/pharo-core] ec7b0e: 60137

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: ec7b0efd3372758bb785c059576ee2264986477b https://github.com/pharo-project/pharo-core/commit/ec7b0efd3372758bb785c059… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-07-06 (Wed, 06 Jul 2016) Changed paths: M Epicea.package/EpClassRemoval.class/instance/accessing/behaviorAffectedName.st M Epicea.package/extension/Class/instance/asEpiceaRingDefinition.st M Graphics-Canvas.package/FormCanvas.class/instance/other/warpFrom_toRect_.st M Graphics-Display Objects.package/Form.class/instance/analyzing/rectangleEnclosingPixelsNotOfColor_.st M Graphics-Display Objects.package/Form.class/instance/scaling%2C rotation/magnify_by_smoothing_.st M Graphics-Primitives.package/BitBlt.class/class/deprecated/current.st M OpalCompiler-Core.package/DebuggerMethodMapOpal.class/instance/public/tempNamed_in_.st M OpalCompiler-Core.package/DebuggerMethodMapOpal.class/instance/public/tempNamed_in_put_.st M OpalCompiler-Core.package/DebuggerMethodMapOpal.class/instance/public/tempNamesForContext_.st A OpalCompiler-Tests.package/OCContextTempMappingTest.class/instance/test - block arguments/testAccessingBlockArgumentNoneOptimizedBlock.st A OpalCompiler-Tests.package/OCContextTempMappingTest.class/instance/test - block arguments/testAccessingBlockArgumentOptimizedBlock.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60136.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60137.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60136.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60137.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60137 18690 deprecated BitBlt class>>#current https://pharo.fogbugz.com/f/cases/18690 17434 debugger missing block local var for optimized blocks https://pharo.fogbugz.com/f/cases/17434 18674 Turn spotter catalog off by default https://pharo.fogbugz.com/f/cases/18674 18608 Impossible to delete a class https://pharo.fogbugz.com/f/cases/18608 http://files.pharo.org/image/60/60137.zip

July 6, 2016

Re: [Pharo-dev] confused about the "image opening session"

by Christophe Demarey

yes, what is bad now is that there is âno crash detectorâ. If you quit an image without saving, you will get the epicea browser. I do not want it in this case. When I do not save, it is on purpose. Maybe a flag should be set when you quit the image (by saving or not). This way, if the flag is not present at image startup, you could guess a crash. > Le 5 juil. 2016 Ã 21:50, stepharo <stepharo(a)free.fr> a Ã©crit : > > Hi > > I saw that we have a new cool feature that presents changes that would have been loaded but not save in the image. > > Now I got confused because several times I prompted with this list and I do not see how I ended up having it > > since I save my image and did not get crash (or idea that I lost changes). > > Is it me that do not understand correctly this feature? > > At the minimum it would be nice to have a little bit more explanation about what is happening. > > Because I imagine new guys coming and seeing this list without any further explanation could be confused. > > Stef > >

July 6, 2016

Re: [Pharo-dev] pharo 5 segfault (stack size?) [FreeBSD]

by Petr Fischer

> On Fri, Jun 17, 2016 at 8:04 PM, Max Leske <maxleske(a)gmail.com> wrote: > > Hi Petr, > > > > That looks like a bug with FreeType with our FFI. It should actually have been fixed but I donât know if the VM for FreeBSD is up to date. Can you post the output of âSmalltalk vm versionâ? > > > > Cheers, > > Max > > > > Petr, Based on Max's suggestion, have you tried turning FreeType off? > World > System > Settings > Apperance > Use Free Type. > IIUC this will fall back to using built-in Strike Fonts [1], and maybe > just bypass the issue?? With FreeType off - still segfaulting. I will move this topic (+ how to debug this segfaults) to the vm mailinglist. Thanks! > > [1] http://pharo.gemtalksystems.com/book/LanguageAndLibraries/fonts_in_pharo/st… > > P.S. Just curious, in the philosophy of trimming down the Pharo Image > size, are Strike Fonts a candidate for removal. It seems like having > an in-Image fall back is potentially useful when porting to new > platforms. > > cheers -ben > > > >> On 17 Jun 2016, at 13:26, Petr Fischer <petr.fischer(a)me.com> wrote: > >> > >> Hello, I got some random segfaults (while loading Seaside) with 32 bit spur vm on FreeBSD - can someone (with low level knowledge) decode attached log? > >> Is this some problem with stack size? Can I fix this? > >> > >> Log: > >> http://pastebin.com/raw/NpFUnjh0 > >> > >> There is "**StackOverflow**" lines n the log... > >> > >> Thanks! pf > >> > > > > >

July 6, 2016

Re: [Pharo-dev] confused about the "image opening session"

by Nicolas Passerini

Me too :) On Tue, Jul 5, 2016 at 9:50 PM, stepharo <stepharo(a)free.fr> wrote: > Hi > > I saw that we have a new cool feature that presents changes that would > have been loaded but not save in the image. > > Now I got confused because several times I prompted with this list and I > do not see how I ended up having it > > since I save my image and did not get crash (or idea that I lost changes). > > Is it me that do not understand correctly this feature? > > At the minimum it would be nice to have a little bit more explanation > about what is happening. > > Because I imagine new guys coming and seeing this list without any further > explanation could be confused. > > Stef > > >

July 5, 2016

confused about the "image opening session"

by stepharo

Hi I saw that we have a new cool feature that presents changes that would have been loaded but not save in the image. Now I got confused because several times I prompted with this list and I do not see how I ended up having it since I save my image and did not get crash (or idea that I lost changes). Is it me that do not understand correctly this feature? At the minimum it would be nice to have a little bit more explanation about what is happening. Because I imagine new guys coming and seeing this list without any further explanation could be confused. Stef

July 5, 2016

Re: [Pharo-dev] Bug in MailA

by stepharo

tx Bernhard! Le 3/7/16 Ã 13:25, Bernhard Pieber a Ã©crit : > Done! > > Cheers, > Bernhard > >> Am 03.07.2016 um 00:08 schrieb Ben Coman <btc(a)openinworld.com>: >> >> On Sun, Jul 3, 2016 at 3:16 AM, Bernhard Pieber <bernhard(a)pieber.com> wrote: >>> Hi, >>> >>> The following code goes into an endless loop: >>> MailAddressParser addressesIn: 'romeo&julia@verona.itâ >>> >>> Itâs because of the ampersand. The fix is trivial, because the bug just was a typo. >>> >>> Fix and test are in the Pharo50Inbox: >>> Network-Mail-BernhardPieber.46.mcz >>> Network-Tests-BernhardPieber.14.mcz >>> >>> Cheers, >>> Bernhard >> Thanks Bernhard. >> Can you log an issue for it on >> and submit this in Slice format. >> Instructions at http://pharo.org/contribute-propose-fix >> This makes it easier to review and the integration system only works >> with Slices & Configurations. >> >> cheers -ben > >

July 5, 2016

Re: [Pharo-dev] ShortArray, DoubleArray & influence of 64bit

by ClÃ©ment Bera

Hi On Tue, Jul 5, 2016 at 4:21 PM, Thibault Raffaillac < thibault.raffaillac(a)inria.fr> wrote: > Hi all, > > For a few months now I have been using IntegerArray and FloatArray with > UFFI. They are pretty convenient since they reside in Internal memory space > (unlike FFIExternalArray) yet you can pass them in a C function call with > the "ByteArray" signature. > Now I need the equivalent arrays for short, double words and IEEE 64bit > double. Comment in > Class>>variableWordSubclass:instanceVariableNames:classVariableNames:package: > says Spur already supports them. From discussion with Guille it seems we > just need new subclasses of BitsLayout (ByteLayout and WordLayout > implemented so far). > > Question 1: What is the value of instanceSpecification for shorts and > double-words? > I copy the comment of Behavior>>instSpec *instSpec* * "Answer the instance specification part of the format that defines what kind of object* * an instance of the receiver is. The formats are* * 0 = 0 sized objects (UndefinedObject True False et al)* * 1 = non-indexable objects with inst vars (Point et al)* * 2 = indexable objects with no inst vars (Array et al)* * 3 = indexable objects with inst vars (MethodContext AdditionalMethodState et al)* * 4 = weak indexable objects with inst vars (WeakArray et al)* * 5 = weak non-indexable objects with inst vars (ephemerons) (Ephemeron)* * 6 = unused* * 7 = immediates (SmallInteger, Character)* * 8 = unused* * 9 = 64-bit indexable* * 10-11 = 32-bit indexable (Bitmap)* * 12-15 = 16-bit indexable* * 16-23 = 8-bit indexable* * 24-31 = compiled methods (CompiledMethod)"* > > Question 2: Both IntegerArray and WordArray exist and refer to 32bit > arrays, should there be a difference between the two? > > Yes. IntegerArray has two specific accessing primitives to store and read raw integers. WordArray uses the normal accessing primitives. Question 3: How will it fare with 64bit Spur? Does word refer to 32bit or > 64bit then? Is WordArray/variableWordSubclass growing to 64bit? FloatArray > too? > It depends. ByteArray is a good name and ShortArray is good name, self-explanatory, there is no discussion here. Then it depends, at some place we use WordArray and DoubleWordArray, in other we use LongArray and SixtyFourBitsIndexableArray... I'd go for WordArray and DoubleWordArray, but I don't mind if one decides otherwise. For Float, we changed the representation to be "SmallFloat64" and "BoxedFloat64". We have no proper support for single precision float in Pharo. We could consider renaming FloatArray to DoubleArray, Float64Array, or something similar. I don't know. > Cheers, > Thibault > >

July 5, 2016

ShortArray, DoubleArray & influence of 64bit

by Thibault Raffaillac

Hi all, For a few months now I have been using IntegerArray and FloatArray with UFFI. They are pretty convenient since they reside in Internal memory space (unlike FFIExternalArray) yet you can pass them in a C function call with the "ByteArray" signature. Now I need the equivalent arrays for short, double words and IEEE 64bit double. Comment in Class>>variableWordSubclass:instanceVariableNames:classVariableNames:package: says Spur already supports them. From discussion with Guille it seems we just need new subclasses of BitsLayout (ByteLayout and WordLayout implemented so far). Question 1: What is the value of instanceSpecification for shorts and double-words? Question 2: Both IntegerArray and WordArray exist and refer to 32bit arrays, should there be a difference between the two? Question 3: How will it fare with 64bit Spur? Does word refer to 32bit or 64bit then? Is WordArray/variableWordSubclass growing to 64bit? FloatArray too? Cheers, Thibault

July 5, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60136 Home: https://github.com/pharo-project/pharo-core

July 5, 2016