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

[pharo-project/pharo-core] b6f7fb: 60140
by GitHub July 7, 2016

July 7, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: b6f7fb4f49a031aac861ae87409687c3ac80f744 https://github.com/pharo-project/pharo-core/commit/b6f7fb4f49a031aac861ae87… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-07-07 (Thu, 07 Jul 2016) Changed paths: M FileSystem-Smalltalk.package/extension/CompiledMethod/instance/fileSize.st M GT-InspectorExtensions-Core.package/extension/CompiledMethod/instance/gtInspectorSourceIn_.st M GT-SpotterExtensions-Core.package/extension/CompiledMethod/instance/spotterPreviewCodeIn_.st M Glamour-Examples.package/GLMBasicExamples.class/instance/others/watcher.st M Glamour-Morphic-Brick.package/GLMCompositeBrick.class/class/examples/gtExamplePharoMethod.st M Kernel.package/CompiledMethod.class/instance/source code management/getSource.st M Network-Mail.package/MailAddressTokenizer.class/class/initialization/initialize.st M Network-Tests.package/MailAddressParserTest.class/instance/tests/testAddressesIn.st A Network-Tests.package/MailAddressParserTest.class/instance/tests/testAmpersand.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/examples/pushClosureCopyNoCopied.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/examples/pushClosureCopyNoCopiedArg.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/examples/pushClosureCopyOneCopiedArg.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/examples/remoteTemp.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/examples/remoteTempNested.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests - blocks/testPushClosureCopyNoCopied.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests - blocks/testPushClosureCopyNoCopiedArg.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests - blocks/testPushClosureCopyOneCopiedArg.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests - blocks/testPushClosureCopyOneCopiedTemp.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests - examples/testDecompileBytecodeDecompilerTestClass.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests - examples/testDecompileBytecodeGeneratorTest.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests - examples/testDecompileIRBuilderTestClass.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testBugOffset.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testDup.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testInstVar.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testJumpAheadTo.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testJumpAheadToIf.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testJumpBackTo.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testLiteralArray.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testLiteralBoolean.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testLiteralCharacter.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testLiteralFloat.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testLiteralInteger.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testLiteralNil.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testLiteralString.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testLiteralSymbol.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testLiteralVariableClass.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testLiteralVariableClassVariable.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testLiteralVariableGlobale.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testPopTop.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testPushConsArray.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testPushConsArray2.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testPushSelf.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testPushTempArgument.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testPushTempTemp.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testPushThisContext.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testRemoteTemp.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testRemoteTempNested.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testReturnTop.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testSendSuper.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testStoreIntoVariable.st M OpalCompiler-Tests.package/OCBytecodeDecompilerTest.class/instance/tests/testStoreTemp.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60139.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60140.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60139.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60140.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60140 18696 some cleanup for OCBytecodeDecompilerTest for new Bytecode set https://pharo.fogbugz.com/f/cases/18696 18680 Forward port 18676 Endless loop parsing e-mail addresses containing an ampersand https://pharo.fogbugz.com/f/cases/18680 18694 deprecate #getSource https://pharo.fogbugz.com/f/cases/18694 http://files.pharo.org/image/60/60140.zip

1 0

ShortArray, DoubleArray & influence of 64bit
by Thibault Raffaillac July 7, 2016

July 7, 2016

> I copy the comment of Behavior>>instSpec I had missed this one, thanks! > 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. I am still confused with WordArray in Pharo terminology: 32bit or native register size? For the naming I like the Java convention: byte(8), short(16), int(32), long(64). Ideally that would make: ByteArray(8), ShortArray(16), IntegerArray(32), LongArray(64), WordArray(native), DoubleWordArray(native*2) As for floats, one arithmetic on 64bit double is fine, but I think we need both 32bit & 64bit loads/stores, that is having FloatArray(32) and DoubleArray(64). That would make UFFI code consistent among 32bit & 64bit machines . Also in x86 all architectures do IEEE 64bit double arithmetic, so no need for a "native" register size. Thibault

1 0

Failure in Tests Cases
by tesonep＠gmail.com July 6, 2016

July 6, 2016

Hi to all, I have tried to fix the CI process to show the failures and errors in the tests in a more descriptive way, not only showing the failed test case, but also the error and the stack trace of it. After checking the problem, I have seen that the failures (and also errors) are not registered with the Error that has produce the failure. Of course, then I remembered that is why the TestRunner reruns the tests to allow the debugging of the error. What do you think of adding the produced exception to the TestResult? Do you think it can have any other consequences? If it has, what if only adding to the CI process? Or perhaps storing a reduced version of the error (perhaps a String representation, or something a lighter than the Error) Thanks for all. -- Pablo Tesone. tesonep(a)gmail.com

2 1

[pharo-project/pharo-core]
by GitHub July 6, 2016

July 6, 2016

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

1 0

[pharo-project/pharo-core] 382ab2: 60139
by GitHub July 6, 2016

July 6, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 382ab247b7ff419185670b875e426a6d80765eab https://github.com/pharo-project/pharo-core/commit/382ab247b7ff419185670b87… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-07-06 (Wed, 06 Jul 2016) Changed paths: R Glamour-Morphic-Brick.package/GLMBrick.class/instance/brick-structure-testing/isFirstInOwner.st M Glamour-Morphic-Brick.package/GLMBrickStructureTrait.class/instance/brick-structure-testing/isFirstInOwner.st M Glamour-Morphic-Brick.package/GLMBrickStructureTrait.class/instance/brick-structure-testing/isLastInOwner.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60138.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60139.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60138.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60139.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Slot.package/AbstractClassModification.class/instance/accessing/layout_.st M Slot.package/extension/Behavior/instance/layout.st M Slot.package/extension/Behavior/instance/layout_.st M Traits.package/TBehavior.class/instance/accessing/typeOfClass.st Log Message: ----------- 60139 16636 Rename layout to classLayout (step 4 deprecate) https://pharo.fogbugz.com/f/cases/16636 18449 Glamour: "Do not use #ifNotNilDo:ifNil:, #ifNil:ifNotNilDo:, #ifNotNilDo:" https://pharo.fogbugz.com/f/cases/18449 http://files.pharo.org/image/60/60139.zip

1 0

Pharo Launcher ?
by Sven Van Caekenberghe July 6, 2016

July 6, 2016

Hi, So I finally started using Pharo Launcher (yes I know, too late) and it is really great ! Where is the documentation for it ? Why is it not mentioned on the main download page ? Where is its landing page, quick reference, 1-2-3 getting started web page ? I went via http://files.pharo.org/platform/launcher/ but that is highly technical and certainly not for first time users. We have to promote this better. Sven

2 1

[pharo-project/pharo-core]
by GitHub July 6, 2016

July 6, 2016

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

1 0

[pharo-project/pharo-core]
by GitHub July 6, 2016

July 6, 2016

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

1 0

pharo 5 segfault (stack size?) [FreeBSD]
by Petr Fischer July 6, 2016

July 6, 2016

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

5 11

Bug in MailA
by Bernhard Pieber July 5, 2016

July 5, 2016

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

6 10