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

[pharo-project/pharo-core] 3f8755: 50747

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 3f875585d1f8aea04c53a5c54bf2203356b5ac4a https://github.com/pharo-project/pharo-core/commit/3f875585d1f8aea04c53a5c5… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-03 (Tue, 03 May 2016) Changed paths: R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50746.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50747.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50746.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50747.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-OSEnvironments.package/OSEnvironment.class/instance/private/getEnv_.st Log Message: ----------- 50747 18139 getenv() call on Ubuntu 14.04 (32 bit) fails in one-click image https://pharo.fogbugz.com/f/cases/18139 http://files.pharo.org/image/50/50747.zip

May 3, 2016

[pharo-project/pharo-core]

by GitHub

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

May 3, 2016

[pharo-project/pharo-core] 619a43: 50746

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 619a43cc29c4db74eef442e345c6ecc5cbcc3b8e https://github.com/pharo-project/pharo-core/commit/619a43cc29c4db74eef442e3… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-03 (Tue, 03 May 2016) Changed paths: R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50745.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50746.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50745.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50746.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50746 18150 AST-FFI-Pharo50Compatibility-EstebanLorenzano.1.mcz missing https://pharo.fogbugz.com/f/cases/18150/ http://files.pharo.org/image/50/50746.zip

May 3, 2016

Paginated list view in GTInspector

by Denis Kudriashov

Hi. Does FastTable will replace paginated list view in GTinspector? Is it planned?

May 3, 2016

Re: [Pharo-dev] Keep print-it output on the same line in GTPlayground

by Peter UhnÃ¡k

> > the conclusion was to print the result on the next line. > Well this isn't true for the last line. The problem isn't just that it prints on the next line for the intermediate results, but that it puts it before the next content. Even if it was on a line of it's own it would be much better. Peter

May 3, 2016

Re: [Pharo-dev] Keep print-it output on the same line in GTPlayground

by Andrei Chis

Hi Pavel, >From what I remember there were some discussions last year when we added this feature and the conclusion was to print the result on the next line. Maybe we can find a better heuristic for placing the result. Cheers, Andrei On Tue, May 3, 2016 at 9:44 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Andrei, > > what is the reason for placing print-it result alway at the end of line? > See atEndOfLineInsertAndSelect:. > > Cheers, > -- Pavel > > > 2016-05-03 9:27 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > >> Hi, >> >> currently when you print the last statement in the playground and press >> enter (to insert the comment into the playground) it outputs it after, >> which is good. >> >> However if I then go back and evaluate a line above, it places the output >> on the _next_ line, just before the next statement, which is quite annoying. >> >> >> >> >> â >> Can this be changed, so it keeps it in line like this? >> >> >> â >> Thanks, >> Peter >> > >

May 3, 2016

Re: [Pharo-dev] Keep print-it output on the same line in GTPlayground

by Pavel Krivanek

ehm, always 2016-05-03 9:44 GMT+02:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: > Andrei, > > what is the reason for placing print-it result alway at the end of line? > See atEndOfLineInsertAndSelect:. > > Cheers, > -- Pavel > > > 2016-05-03 9:27 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > >> Hi, >> >> currently when you print the last statement in the playground and press >> enter (to insert the comment into the playground) it outputs it after, >> which is good. >> >> However if I then go back and evaluate a line above, it places the output >> on the _next_ line, just before the next statement, which is quite annoying. >> >> >> >> >> â >> Can this be changed, so it keeps it in line like this? >> >> >> â >> Thanks, >> Peter >> > >

May 3, 2016

Re: [Pharo-dev] Keep print-it output on the same line in GTPlayground

by Pavel Krivanek

Andrei, what is the reason for placing print-it result alway at the end of line? See atEndOfLineInsertAndSelect:. Cheers, -- Pavel 2016-05-03 9:27 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > Hi, > > currently when you print the last statement in the playground and press > enter (to insert the comment into the playground) it outputs it after, > which is good. > > However if I then go back and evaluate a line above, it places the output > on the _next_ line, just before the next statement, which is quite annoying. > > > > > â > Can this be changed, so it keeps it in line like this? > > > â > Thanks, > Peter >

May 3, 2016

Keep print-it output on the same line in GTPlayground

by Peter UhnÃ¡k

Hi, currently when you print the last statement in the playground and press enter (to insert the comment into the playground) it outputs it after, which is good. However if I then go back and evaluate a line above, it places the output on the _next_ line, just before the next statement, which is quite annoying. â Can this be changed, so it keeps it in line like this? â Thanks, Peter

May 3, 2016

New Cog VMs available

by Eliot Miranda

... at http://www.mirandabanda.org/files/Cog/VM/VM.r3692 These include stack ARM VMs for Spur and V3. CogVM binaries as per VMMaker.oscog-eem.1855/r3692 General: Fix a bad bug in primitiveVoidVMStateForMethod. One might think that the heap scan is unnecessary if the method does not have a cog method. But it could be the case that the code zone has recently been reclaimed and so not having a cog method is no indication that it didn't have a cog method some time in the recent past, and that there are indeed still contexts with machine code pcs out there. Correct slip in primitiveMethodXray, the flags were not set in each caseOf: branch (thanks to -Wunused-value). Change overflow tests in precondition rather than postcondition for small integer multiplication. Because integer overflow is undefined behaviour, and because we can't rely on undefined behaviour, the compiler has a license to eliminate the post-condition as dead code (at least since iso c89 acception). Post-condition currently works because we use -fwrapv compiler flag, but relying on specific compiler flags is bad practice in the long term. Fix regression in signed 32bit long access (introduced beginning of April). One symptom is: (Alien newGC: 4) signedLongAt: 1 put: -16r7287E552; signedLongAt: 1 Fix positive32BitIntegerFor: for Spur64 which worked only because the constant was generated ULL. Spur: Fix primitiveIsPinned. V3: Fix missing comparison operation in genPrimitiveIdentical on V3. This should fix Character = problem encounterd in Cuis. Debugging: Add printContextReferencesTo: & printActivationsOf: and have them print the pcs of the contexts they find. Cogit: Reorder annotation constants to simplify isPCMappedAnnotation:. Sista Cogit: Added a primitive to answer all the methods present in the machine code zone. allMachineCodeMethods <primitive: 'primitiveAllMethodsCompiledToMachineCode' module:''> ^#() Fix regression in VMMaker.oscog-eem.1823 when merging the two map enumerators into one that affects Sista. The merged enumerator must extend IsSendAnnotations with the AnnotationExtension. Plugins: Regenerate plugins using the recently revised type inferrence code. Slang: Extend type inference capabilities from the AST. Unify type inference used to #inferReturnTypeFromReturnsIn: with that based on AST. Now that type inference is a bit more thorough, release type restrictions in #isFunctional in order to obtain much more aggressive inlining. With those, a gain of 10% is possible on the LargeIntegersPlugin dominated bench: Use a type inference that better fits C rules (C99 standard section 6.3): - in (float op int), int is promoted to double not float - in (unsigned short op short) both operands are promoted to #int due to int promotion rules. Use minimum generality for generated integer constants: - use int if variable fits in int - else unsigned int - else long long (long would be enough for 64bits versions, but long long works for both 32 and 64) - else unsigned long long This is to avoid spurious unsigned promotion due to improved type inference. Mac OS X: Fix argument processing, so that e.g. myvm -breaksel aSelector my.image works (but -headless still fails). _,,,^..^,,,_ best, Eliot

May 3, 2016