- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]
by GitHub April 10, 2015

April 10, 2015

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

1 0

[pharo-project/pharo-core]
by GitHub April 10, 2015

April 10, 2015

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

1 0

[pharo-project/pharo-core] 3a052a: 40600
by GitHub April 10, 2015

April 10, 2015

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 3a052a44e5533b9f63e06afe560ddce92e7306cf https://github.com/pharo-project/pharo-core/commit/3a052a44e5533b9f63e06afe… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-04-10 (Fri, 10 Apr 2015) Changed paths: M KernelTests.package/FloatTest.class/instance/tests - NaN behavior/testNaNCompare.st A Manifest-Core.package/extension/RPackageTag/instance/manifestBuilderForRuleChecker_.st M NautilusCommon.package/extension/CompiledMethod/instance/isExampleMethod.st M OSWindow-Core.package/OSWindowTest.class/instance/as yet unclassified/testNewWindowDefaults.st M OSWindow-Core.package/OSWindowTest.class/instance/as yet unclassified/testSettingUpWindow.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script599.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script600.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40599.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40600.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40600 15325 DNU running code critics on a package tag https://pharo.fogbugz.com/f/cases/15325 15225 useless play icon in nautilus https://pharo.fogbugz.com/f/cases/15225 15316 FloatTest>>#testNaNCompare fails with new VM https://pharo.fogbugz.com/f/cases/15316 15318 Two tests in OSWindowTest fail on Windows with new VM https://pharo.fogbugz.com/f/cases/15318 http://files.pharo.org/image/40/40600.zip

1 0

[pharo-project/pharo-core]
by GitHub April 10, 2015

April 10, 2015

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

1 0

[pharo-project/pharo-core] ea6cb4: 40599
by GitHub April 10, 2015

April 10, 2015

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: ea6cb4930b8e733de7bdf9f41a686ee14f7efb41 https://github.com/pharo-project/pharo-core/commit/ea6cb4930b8e733de7bdf9f4… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-04-10 (Fri, 10 Apr 2015) Changed paths: M Monticello.package/MCMethodDefinition.class/instance/comparing/=.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script598.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script599.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40598.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40599.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Inspector.package/EyeTreeInspector.class/instance/api/childrenForObject_.st Log Message: ----------- 40599 15321 Monticello marks all methods of a package as new/changed https://pharo.fogbugz.com/f/cases/15321 15319 Basic Inspector: MNU when switching to tree https://pharo.fogbugz.com/f/cases/15319 http://files.pharo.org/image/40/40599.zip

1 0

Existing <script> <example> pragmas and new GT needs
by Torsten Bergmann April 10, 2015

April 10, 2015

Hi Tudor and all, to understand the issue one has to know: ------------------------------------------------------------------------------------------ There are two pragmas in Pharo 4 that were already introduced and integrated: <script> / <script:> - one can use this to mark methods (of any signature) as development scripts. One can use it on instance side and an class side methods to run the method or some code while developing without having to leave the browser. After completion Nautilus shows that the method finished Think of a class "MyKillerProjectDatabase" with a class side method "start". You can click this to run - but it does not serve as an example. A script is just "SOMETHING TO RUN". The code of the script may be too easy or to complicated to serve as an example. See also #14647, #14747 and #14995 for details. <example> - Nautilus in the past already honored class side exampleXXX methods to have a "play" icon to easily visually see examples and just run them. With the <example> pragma one can explicitly mark a method as an example method and we do not have to rely on the method name. So we can use #tryThisOutForExample as selector name as well now. It also allows to search for examples, build an example browser for newbees, ... An example shows the usage of a class or code (usually to get an initial idea). The pragma also only works on class side methods. Think of existing classes like EditableList or WidgetExamples that provide example methods starting with exampleXXX. The user sees in the browser directly that this is an example he can run or look at to understand the details because the author offered it as "SOMETHING TO LEARN FROM". See also #14646 and #15225 for details So (even only at the second look) there is a distinction between a "script" and an "example". Being a script does not automagically make a method an example. And yes: a method can also be both and both pragmas can be used. The history of these two is explained in https://pharo.fogbugz.com/f/cases/15225/useless-play-icon-in-nautilus and I already use this in several projects. -------------------------------------------------------------------------------------------- Now it looks like Tudor is in need of a pragma for GT tools to provide "example data". @Tudor: I do not understand why you now abuse/try to redefine the meaning of this existing <example> pragma for your special purposes/needs or try to exchange one against the other as in new issue #15229. According to your own comment in issue #15225 your definition of an "example" is something "to offer an initialized object that can be used for documentation or testing purposes." I have to strongly disagree on this as this is ONLY TRUE FOR A FEW CASES. Look at our image, look at how people write example (methods): NOT ALL class side example methods necessarily return an initialized objects but are still examples. I already explained in the above issue that there are lots of example methods that one just run (either from the comment or from Nautilus icon) like EditableListExampel(class)>>example, ... They DO NOT return an initialized instance. Look at the "examples" in class WidgetExamples or others. None of them provide an initialized instance! So the right definition for an "example" is: "to offer runnable code that can be used for documentation or testing purposes." So PLEASE if you are in need of such a new thing where only initialized instances are returned from code then DO NOT REDEFINE existing and used pragmas like the integrated <example> pragma. PLEASE use an OWN NEW PRAGMA for GT purposes like <exampleData>, <exampleInstance>, <gtExampleInstance> or whatever. I would also find an "exampleInstance" pragma name then more intention revealing. Thanks a lot in in advance! Bye T.

14 54

source code mgmt issues in Pharo4
by Johan Brichau April 10, 2015

April 10, 2015

Hi all, Over the last week, I started working with Pharo4, mostly to make Seaside work cleanly. On several occasions, I had severe issues with the package management: - methods that were changed in a class were not recorded as âchangedâ in monticello and were absent from the published package - versions of methods disappeared (i.e. no longer accessible in the version history of a method) - looking at the âchangedâ in Monticello showed all code of the package as changed (though only a single method has changed). This makes working with Pharo4 extremely problematic. I cannot trust the source code packaging/publishing and merging anymore. I cannot discern a scenario that leads to these issues but I do have an image right now where I only changed a single method and the entire package shows up as âchangedâ. Anyone experience similar issues? Johan

3 4

New Cog VMs available
by Eliot Miranda April 10, 2015

April 10, 2015

... at http://www.mirandabanda.org/files/Cog/VM/VM.r3308/. CogVM binaries as per VMMaker.oscog-eem.1178/r3308 Plugins: Integrate Nicolas' fixes that use positiveMachineIntegerFor: for pointers. Newspeak: Print a warning in the method shared under multiple selectors scenario. Implement outer sends as clean sends just like implicit receiver sends. Add ObjectRepresentation>>illegalClassTag and use it for initializing and unlinking implicit and outer sends. Newspeak & Sista: The multiple bytecode set block initial nil counters need to be specific to the bytecode set in effect. Spur: Implement Clement's much better solution for the stale supersend problem. Place code at the send site for super sends to follow stale forwarded receivers. This parallels the interpreter implementation. Beef up the post-become scan of send sites to unlink all send sites that link to an invalid class tag. Cogit: Optimize StackToRegisterMappingCogit>>genReturnReceiver to not load ReceiverResultReg if it already contains self. Revise method map generation to provide multiple send type annotations. Add an IsAnnotationExtension annotation type that implicitly has a zero displacement and uses its displacement bits to extend the preceeding IsSendCall annotation. This allows us to eliminate all the exotic entry-points and keep only the checked and unchecked entries. Change IA32's genPushRegisterArgsForNumArgs: to not smash TempReg now that it is used in directed super send trampolines. Use PushCq to pass small integer constants in the trampolines instead of smashing TempReg, which is now used to hold the directed supersend argument. Add support for PushCq. Could use PushCw but on x86 PushCq is a lot shorter. Mac builds: Use UTC as the timezone for the build timestamp. Using the local timezone doesn't work :(. -- best, Eliot

3 3

broken setting in FFI
by Richard Wettel April 9, 2015

April 9, 2015

Hi I bumped into a broken setting in FFI (see attached Screenshot). After I exported the settings, every time I open an image a DNU comes to greet me: NBGlxAPI class>>moduleName: >From the implementation, it seems the setting does not make much sense. Or if it does to somebody, it is probably still missing some part. Cheers Ricky

5 8

almost ready to release except for two bugs
by Esteban Lorenzano April 9, 2015

April 9, 2015

Hi, Soâ¦ subject says all. We need to fix this two: - https://pharo.fogbugz.com/f/cases/14606 <https://pharo.fogbugz.com/f/cases/14606> - the NOT REPORTED IN TRACKER MC BUG! (What are you thinking guys? Report, report, REPORT!â¦ I failed the Jedi examenâ¦ without report the bug does not exist) and we are ready to go. Of course, we will try to fix between today and tomorrowâ¦ but even if we succeed, since âyou shall not go into production a fridayâ, release will be monday. cheers, Esteban

4 4