- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] 20a69e: 40382
by GitHub Nov. 22, 2014

Nov. 22, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 20a69ec3f950e4f88ed083008aa723692100bd38 https://github.com/pharo-project/pharo-core/commit/20a69ec3f950e4f88ed08300… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-11-22 (Sat, 22 Nov 2014) Changed paths: A Morphic-Base.package/extension/BorderedMorph/instance/changeBorderColor_.st M Morphic-Core.package/BorderedMorph.class/instance/menu/addBorderStyleMenuItems_hand_.st A Polymorph-Tools-Diff.package/PSMCChangesGrouper.class/instance/visitor/visitClassTraitDefinition_.st M Refactoring-Core.package/RBAbstractClass.class/instance/accessing/allSubclasses.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script382.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40382.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40382 14516 use an explicit copy of subclass collection in RBAbstractClass>>#allSubclasses https://pharo.fogbugz.com/f/cases/14516 12007 BorderMorph halo menu border colour broken https://pharo.fogbugz.com/f/cases/12007 14494 PSMCChangesGrouper is missing #visitClassTraitDefinition: https://pharo.fogbugz.com/f/cases/14494 http://files.pharo.org/image/40/40382.zip

1 0

[pharo-project/pharo-core]
by GitHub Nov. 22, 2014

Nov. 22, 2014

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

1 0

Float hierarchy for 64-bit Spur
by Eliot Miranda Nov. 21, 2014

Nov. 21, 2014

Hi All, 64-bit Spur can usefully provide an immediate float, a 61-bit subset of the ieee double precision float. The scheme steals bits from the mantissa to use for the immediate's 3-bit tag pattern. So values have the same precision as ieee doubles, but can only represent the subset with exponents between 10^-38 and 10^38, the single-precision range. The issue here is how to organize the class hierarchy. The approach that looks best to me is to modify class Float to be an abstract class, and add two subclasses, BoxedFloat and SmallFloat, such that existing boxed instances of Float outside the SmallFloat range will become instances of BoxedFloat and instances within that range will be replaced by references to the relevant SmallFloat. With this approach ... - Float pi etc can still be used, even though they will answer instances of SmallFloat. But tests such as "self assert: result class == Float." will need to be rewritten to e.g. "self assert: result isFloat". - BoxedFloat and SmallFloat will not be mentioned much at all since floats print themselves literally, and so the fact that the classes have changed won't be obvious. - the boxed Float primitives (receiver is a boxed float) live in BoxedFloat and the immediate ones live in SmallFloat. Making SmallFloat a subclass of Float poses problems for all the primitives that do a super send to retry, since the boxed Float prims will be above the unboxed ones and so the boxed ones would have to test for an immediate receiver. An alternative, that VW took (because it has both Float and Double) is to add a superclass, e.g. LimitedPrecisionReal, move most of the methods into it, and keep Float as Float, and add SmallFloat as a subclass of LimitedPrecisionReal. Then while class-side methods such as pi would likely be implemented in LimitedPrecisionReal class, sends to Float to access them find them via inheritance. An automatic reorganization which moves only primitives out of LimitedPrecisionReal is easy to write. Thoughts? -- best, Eliot

5 4

Re: [Pharo-dev] [squeak-dev] Float hierarchy for 64-bit Spur
by Eliot Miranda Nov. 21, 2014

Nov. 21, 2014

Hi Tobias, On Fri, Nov 21, 2014 at 4:51 AM, Tobias Pape <Das.Linux(a)gmx.de> wrote: > Hi, > > On 21.11.2014, at 13:44, Bert Freudenberg <bert(a)freudenbergs.de> wrote: > > > On 21.11.2014, at 13:29, J. Vuletich (mail lists) < > juanlists(a)jvuletich.org> wrote: > > > >> Quoting Bert Freudenberg <bert(a)freudenbergs.de>: > >>> > >>> I'd suggest BoxedDouble and ImmediateDouble as names for the concrete > subclasses (*). Names do mean something. (**) > >>> > >>> You're right about the FloatArray confusion. However, note that the > IEEE standard calls it single and double. It's only C using "float" to mean > "single precision". > >>> > >>> I'd name the abstract superclass Float, for readability, and the > isFloat test etc. Also: "Float pi" reads a lot nicer than anything else. I > don't see the need for having a deep LimitedPrecisionReal - Float - > BoxedDouble/ImmediateDouble deep hierarchy now. > >>> > >>> If we ever add single-precision floats, we should name them > BoxedSingle and ImmediateSingle. At that point we might want a Single > superclass and a LimitedPrecisionReal supersuperclass, but we can cross > that bridge when we get there. > >>> > >>> - Bert - > >>> > >>> (*) Since we're not going to see the class names often, we could even > spell it out as BoxedDoublePrecisionFloat and > ImmediateDoublePrecisionFloat. Only half joking. It would make the relation > to the abstract Float very clear. > >>> > >>> (**) We could also try to make the names googleable. I was surprised > to not get a good hit for "boxed immediate". Only "boxed unboxed" finds it. > Maybe there are two better words? > >> > >> I very much agree with Bert. But I'd suggest SmallDouble instead of > ImmediateDouble for consistency with SmallInteger. > > > > Then it would have to be LargeDouble for consistency with LargeInteger, > too. Which I don't find compelling. > > > > Also, with the 64 bit format we get many more immediate objects. There > already are immediate integers and characters, floats will be the third, > there could be more, like immediate points. For those, the small/large > distinction does not make sense. > > > > Maybe Eliot's idea of keeping "Float" in the name was best, but instead > of "small" use "immediate": > > > > Float - BoxedFloat - ImmediateFloat > > > > A Float is either a BoxedFloat or an ImmediateFloat, depending on > the magnitude of its exponent. > > I don't like the idea of putting a VM/Storage detail into the Class name. > The running system itself does not care about whether Floats or Integers > are > boxed or immediate. > I disagree. I think at least Smalltalk-80 has a philosophy of lifting as much out of the VM into the system, and hiding it from clients via encapsulation. So unlike many other VMs the compiler is in the system, the system explicitly separates SmallInteger, LargePositiveInteger and LargeNegativeInteger and implements large integer arithmetic with Smalltalk code that uses SmallIntegers. Note that the primitives are an optional extra optimization that the VM does not need to implement. So for me it is in keeping with the current system to use BoxedFloat and SmallFloat or BoxedDouble and SmallDouble. This lifting things up provides us with an extremely malleable system. Pushing things down into the VM does the opposite. For example in RSqueakVM (aka SPy) there is no immediate > Integer whatsoever. Yes, tagged ints are read during image startup but they > aren't subsequently represented as immediates or tagged ints after that. > Well because it's implemented above RPython I guess it is using Python's bignum code directly. That's fine but its a bit of a cheat. > > Just as input, in the Racket language and other Schemes, > the equivalent to our SmallInterger/LargeInteger is fixnum/bignum > and for floats they have flonums and "extflonums" (80bit). > > Best > -Tobias thanks -- best, Eliot

2 3

[pharo-project/pharo-core]
by GitHub Nov. 21, 2014

Nov. 21, 2014

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

1 0

[pharo-project/pharo-core] 898184: 40381
by GitHub Nov. 21, 2014

Nov. 21, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 89818487a755292e8f477a5e855cdca5b578b619 https://github.com/pharo-project/pharo-core/commit/89818487a755292e8f477a5e… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-11-21 (Fri, 21 Nov 2014) Changed paths: R Collections-Abstract.package/Collection.class/instance/enumerating/do_displayingProgress_.st R Collections-Abstract.package/Collection.class/instance/enumerating/do_displayingProgress_every_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script381.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40381.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A System-Caching.package/extension/BlockClosure/instance/memoized.st A System-Caching.package/extension/BlockClosure/instance/memoizedUsing_.st A System-CachingTests.package/extension/BlockClosureTest/instance/testMemoizedDictionary.st A System-CachingTests.package/extension/BlockClosureTest/instance/testMemoizedLRUCache.st A System-CachingTests.package/extension/LRUCache/instance/testSupportGetCachedAssociations.st A UIManager.package/extension/Collection/instance/do_displayingProgress_.st A UIManager.package/extension/Collection/instance/do_displayingProgress_every_.st Log Message: ----------- 40381 14487 do:displayingProgress: in Collection should be part of the UIManager package https://pharo.fogbugz.com/f/cases/14487 14458 Add BlockClosure>>memoized https://pharo.fogbugz.com/f/cases/14458 http://files.pharo.org/image/40/40381.zip

1 0

Glorp and DBXTalk
by Hernan Wilkinson Nov. 21, 2014

Nov. 21, 2014

Hi, quick question, how can I get Glorp for Pharo? And DBXTalk? If anyone can provide me with some links it will be much appreciated :-) -- *HernÃ¡n WilkinsonAgile Software Development, Teaching & Coaching* *Phone: +54 - 011 - *6091 - 3125 *Mobile: +54 - 911 - 4470 - 7207email: hernan.wilkinson(a)10Pines.comsite: http://www.10Pines.com <http://www.10pines.com/>* Address: Alem 693, Floor 5 B, Buenos Aires, Argentina

2 1

[pharo-project/pharo-core]
by GitHub Nov. 21, 2014

Nov. 21, 2014

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

1 0

[pharo-project/pharo-core] f9a0b8: 40380
by GitHub Nov. 21, 2014

Nov. 21, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: f9a0b80a61c7f7cd29f7a833e93475d87b606d21 https://github.com/pharo-project/pharo-core/commit/f9a0b80a61c7f7cd29f7a833… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-11-21 (Fri, 21 Nov 2014) Changed paths: A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script380.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40380.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Text-Edition.package/SimpleEditor.class/instance/nonediting%2Fnontyping keys/cursorHome_.st M Text-Edition.package/TextEditor.class/instance/nonediting%2Fnontyping keys/cursorHome_.st M Versionner-Spec-Browser.package/VersionnerRepositoriesManager.class/instance/initialization/initializeSelectedRemotes.st Log Message: ----------- 40380 14510 Wrong editing history positions after using home-key https://pharo.fogbugz.com/f/cases/14510 14495 Adding dependent projects in Versionner fails (adding to array instead of collection) https://pharo.fogbugz.com/f/cases/14495 http://files.pharo.org/image/40/40380.zip

1 0

Re: [Pharo-dev] ConfigurationOfGlamour not connected to repository
by Stephan Eggermont Nov. 21, 2014

Nov. 21, 2014

Doru wrote: >Indeed, these are not needed. Those groups are not maintainable and make tool building a nightmare. We will remove them from all Moose configurations eventually :). Sorry, afaik the groups are essential complexity and removing them just increases the problems. Configuration management is essentially a 5-dimensional problem and the tools need to support different workflows so they will never be simple. Stephan

1 0