February 2013 - Pharo-dev - lists.pharo.org

[Pharo-project] Native Boost issue
by S Krish Feb. 7, 2013

Feb. 7, 2013

Find that the NBExternalAddress >> readString returns extra bytes... did a simple cmd pipe interface .. and the readPipe with a buffer passed ends up with 4 bytes extra in specific boundary of passed buffer size. viz: if I pass buf := ( NativeBoost allocate: 4096) as the buffer and then read it as buf readString. The size returned is 4100 instead of 4096. For some other lesser reads occassionally it is off by one byte.. Will try to post a simple example to replicate this.

2 2

[Pharo-project] files.pharo.org
by Marcus Denker Feb. 7, 2013

Feb. 7, 2013

Hi, Now there is a DNS entry and forwarder http://files.pharo.org this works for all files there, e.g. http://files.pharo.org/image/20/latest.zip We will keep these links, even when we move to a dedicated file server. (We have requested one and it should be ready soon, we hope) Marcus

3 2

[Pharo-project] Issues for tomorrow's sprint
by Esteban Lorenzano Feb. 7, 2013

Feb. 7, 2013

Hi, I was going to mark the relevant issues for sprint tomorrow, but there are so few remaining that I'd rather say "let's take them all!"... starting from "work needed" and going down :) cheers, Esteban

1 0

[Pharo-project] [update 2.0] #20521
by Marcus Denker Feb. 7, 2013

Feb. 7, 2013

20521 ----- Issue 7382: TextModel>>setSelection: has no effect if called before openWithSpec http://code.google.com/p/pharo/issues/detail?id=7382 Issue 7389: Behavior not taken into account in TextModel when sending openWithSpec http://code.google.com/p/pharo/issues/detail?id=7389 Diff information: http://ss3.gemstone.com/ss/Pharo20/Spec-Widgets-MarcusDenker.95.diff

1 0

[Pharo-project] [update 2.0] #20520
by Marcus Denker Feb. 7, 2013

Feb. 7, 2013

20520 ----- Issue 7104: ImageCleaner>>#cleanUpForProduction broken (part 1) http://code.google.com/p/pharo/issues/detail?id=7104 Issue 7443: Setting compatible setter/getter to set image wide compiler http://code.google.com/p/pharo/issues/detail?id=7443 Issue 7442: In Settings, Morphic should be capitalized http://code.google.com/p/pharo/issues/detail?id=7442& Diff information: http://ss3.gemstone.com/ss/Pharo20/Tools-MarcusDenker.1032.diff http://ss3.gemstone.com/ss/Pharo20/System-Support-MarcusDenker.773.diff http://ss3.gemstone.com/ss/Pharo20/Morphic-MarcusDenker.1345.diff http://ss3.gemstone.com/ss/Pharo20/Deprecated20-MarcusDenker.30.diff

1 0

[Pharo-project] Future "Modules system"
by Denis Kudriashov Feb. 7, 2013

Feb. 7, 2013

Hello. Some days ago I think about how java works with dependencies and how it can be implemented in smalltalk. For java example libA.jar uses SharedClass.methodA and libB.jar uses SharedClass.methodB. But #methodA exists only in version deployed as libS-a.jar. And #methodB exists only in version deployed as libS-b.jar. Dependency from libA.jar on libS-a.jar and libB.jar on libS-b.jar are defined explicitly in their classpathes. So libA.jar knows nothing about libS-b.jar and v.v. And that's why your java programm can works at same time with libA.jar and libB.jar. They will use different versions of same class. What it means in context of pharo? In pharo we have configurations which manage dependencies of projects. But you can't use at same time projectA and projectB which depend on different versions of projectS (when they both use same SharedClass from projectS like in java example). If you load projectA last you will get SharedClass with only methodA. If you load projectB last you will get SharedClass with only methodB. So projectA and projectB can't works correctly at same time. My example very simple. It includes just single class differencies. It can be more complicated and java world is good example for this. So my global question is how it can be solved in pharo? Do you have some plan for this? I can't remember something similar in pharo vision docs. But maybe what Stephane called "modules system" is exactly about this? I mean what Stephane always opposes in namespaces/environment discussions. And I think that this problem is ortogonal to namespaces/environments support. Do you agree? Do you know about such reseach in smalltalk? Little conclusion about such module system (if we can named it such way?) and what it is required from pharo: - ability to get in image different versions of same package. - separated class (global) dictionaries (multiple Smalltalk's) per package version. Maybe it can be named Module. So let's think about Module as unique Package+Version pair which contains all globals specific to this version and all dependent other Modules. - each Module knows it dependencies from other Modules, This information can be retreived from configuration. - each method and class should know from which project version (module) it was loaded. - inside any methods compiler should resolve class names based on Module dependencies information. Compiler should lookup actual class objects from module dependencies hierarchy. So no global Smalltak for compiler. But Smalltalk can be stay in system as default core Module. - If you want to use class which presents in two loaded versions of same package you should resolve conflict manually. Such action should add dependency to Module of your code. - Module can't have dependencies of two Modules of same package. It means that code of your project can use only version of some dependant class. I think it is essential restriction of Modules system. Main thing which Module system can get to us is ability to safelly load any versions of our projects and use it. It is not matter how old this code. System just loads old version of pharo core for example. Existed pharo core will continue works correctly. So what you think about it? Best regards, Denis

8 21

[Pharo-project] github repository
by Camillo Bruni Feb. 7, 2013

Feb. 7, 2013

I just killed all the file-tree noise (mostly metacello version info) Now we can properly see what changed between pharo versions over all packages: https://github.com/pharo-project/pharo-core/commit/cea99d02a2d0d743880cd7a8… => this will be my major source for debugging information when looking for newly introduced bugs! => using git-bisect it will be super easy to find these bugs

3 3

[Pharo-project] [update 2.0] #20519
by Marcus Denker Feb. 7, 2013

Feb. 7, 2013

20519 ----- Issue 7438: [ENH]: Nautilus Help http://code.google.com/p/pharo/issues/detail?id=7438 Issue 7427: failing test for SmalllintManifestCheckerTest http://code.google.com/p/pharo/issues/detail?id=7427 Issue 7424: [Bug]: Removing a class does not mark the package as dirty http://code.google.com/p/pharo/issues/detail?id=7424 Issue 7209: ChangesBrowser should execute refactorings in order http://code.google.com/p/pharo/issues/detail?id=7209 Diff information: http://ss3.gemstone.com/ss/Pharo20/Spec-Widgets-MarcusDenker.92.diff http://ss3.gemstone.com/ss/Pharo20/RPackage-Core-MarcusDenker.207.diff http://ss3.gemstone.com/ss/Pharo20/NautilusRefactoring-MarcusDenker.71.diff http://ss3.gemstone.com/ss/Pharo20/Nautilus-MarcusDenker.415.diff http://ss3.gemstone.com/ss/Pharo20/Monticello-MarcusDenker.756.diff

1 0

[Pharo-project] [update 2.0] #20518
by Marcus Denker Feb. 7, 2013

Feb. 7, 2013

1 0

[Pharo-project] new Cog VMs available
by Eliot Miranda Feb. 6, 2013

Feb. 6, 2013

http://www.mirandabanda.org/files/Cog/VM/VM.r2678 CogVM binaries as per VMMaker.oscog-eem.264/r2678. Fix snapshot primitive failure in the StackVM and Cogit. The primitive should fail, not merely return the receiver. Also if in Cogit, need to back-up instruction pointer on failure. Make reportMinimumUnusedHeadroom more informative (also print available headroom). -- best, Eliot

1 0