March 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3575 in pharo: [Failing Tests] Obsolete classes after tests
by pharo＠googlecode.com March 18, 2011

March 18, 2011

Updates: Summary: [Failing Tests] Obsolete classes after tests Comment #6 on issue 3575 by guillerm...(a)gmail.com: [Failing Tests] Obsolete classes after tests http://code.google.com/p/pharo/issues/detail?id=3575 (No comment was entered for this change.)

1 5

Re: [Pharo-project] Issue 1914 in pharo: Should check the comments added to packageinfo by andreas in squeak
by pharo＠googlecode.com March 18, 2011

March 18, 2011

Updates: Status: Closed Comment #3 on issue 1914 by marcus.d...(a)gmail.com: Should check the comments added to packageinfo by andreas in squeak http://code.google.com/p/pharo/issues/detail?id=1914 PackageInfo will be replaced by RPackage soon

1 0

Re: [Pharo-project] Issue 953 in pharo: PackageInfo could be much faster
by pharo＠googlecode.com March 18, 2011

March 18, 2011

Updates: Status: FixProposed Comment #20 on issue 953 by marcus.d...(a)gmail.com: PackageInfo could be much faster http://code.google.com/p/pharo/issues/detail?id=953 (No comment was entered for this change.)

1 1

Re: [Pharo-project] GSOC 2010 results
by Marcus Denker March 18, 2011

March 18, 2011

On Mar 18, 2011, at 5:18 PM, Miguel CobÃ¡ wrote: > I think the "No" answer is more like "there are no current plans, > because nobody has pushed it" than "the namespaces implementation is > banned from Pharo" Or: Namespaces can be done so easily wrong so that oe needs to think very carefully and there are no braincycles left just now. At least, that's my view... and I think that the project indeed is very important, as it shows one solution that we can learn from... and then we can realize something for Pharo after we are sure we learned enough. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

3 2

[Pharo-project] Issue 3426 in pharo: shouldBePrintedAsLiteral instead of isLiteral
by pharo＠googlecode.com March 18, 2011

March 18, 2011

Status: Fixed Owner: stephane.ducasse Labels: Milestone-1.3 New issue 3426 by stephane.ducasse: shouldBePrintedAsLiteral instead of isLiteral http://code.google.com/p/pharo/issues/detail?id=3426 Levente Uzonyi uploaded a new version of Kernel to project The Trunk: http://source.squeak.org/trunk/Kernel-ul.518.mcz ==================== Summary ==================== Name: Kernel-ul.518 Author: ul Time: 23 November 2010, 1:54:49.317 pm UUID: b098496d-94bb-f943-9cf9-bd07ab3b0b71 Ancestors: Kernel-dtl.517 - introduced Object >> #shouldBePrintedAsLiteral as a replacement for #isLiteral during printing and storing =============== Diff against Kernel-dtl.517 =============== Item was added: + ----- Method: Object>>shouldBePrintedAsLiteral (in category 'testing') ----- + shouldBePrintedAsLiteral + + ^self isLiteral! Item was changed: ----- Method: ScaledDecimal>>storeOn: (in category 'printing') ----- storeOn: aStream "SxaledDecimal sometimes have more digits than they print (potentially an infinity). In this case, do not use printOn: because it would loose some extra digits" + self shouldBePrintedAsLiteral - self isLiteral ifTrue: [self printOn: aStream] ifFalse: [aStream nextPut: $(; store: fraction numerator; nextPut: $/; store: fraction denominator; nextPut: $s; store: scale; nextPut: $)]!

1 4

[Pharo-project] Issue 3828 in pharo: SimpleMorphic overrides system method
by pharo＠googlecode.com March 18, 2011

March 18, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.2 Milestone-1.3 New issue 3828 by marcus.d...(a)gmail.com: SimpleMorphic overrides system method http://code.google.com/p/pharo/issues/detail?id=3828 .. leading to problem when unloading. Fix attached. Attachments: FixSimpleMorphicUnload.1.cs 910 bytes

1 3

[Pharo-project] Issue 3827 in pharo: parser rejects sending a message to the result of yourself
by pharo＠googlecode.com March 18, 2011

March 18, 2011

Status: Accepted Owner: squirebl...(a)gmail.com New issue 3827 by squirebl...(a)gmail.com: parser rejects sending a message to the result of yourself http://code.google.com/p/pharo/issues/detail?id=3827 Pharo image: dev Pharo core version: Pharo-1.1.1-- Latest update: #11414 Virtual machine used: COG VM for Windows Class browser used if applicable: OBSystemBrowserSteps to reproduce: define this method in the browser addTo: p ^ p add: self; yourself sort and accept; you get addTo: p ^ p add: self; yourself s End of block expected ->ort

1 2

[Pharo-project] [update 1.2] #12343
by Marcus Denker March 18, 2011

March 18, 2011

12343 ----- Issue 3828: SimpleMorphic overrides system method -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3829 in pharo: 1.2 core image needs to allow loading 1.2.1 updates
by pharo＠googlecode.com March 18, 2011

March 18, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.2 New issue 3829 by marcus.d...(a)gmail.com: 1.2 core image needs to allow loading 1.2.1 updates http://code.google.com/p/pharo/issues/detail?id=3829 1.2 core image needs to allow loading 1.2.1 updates else we can not do them

1 1

Re: [Pharo-project] [ANN 1.2] prebuilt core 1.2 final
by Marcus Denker March 18, 2011

March 18, 2011

On Mar 18, 2011, at 8:16 AM, Lukas Renggli wrote: >> I would not unload packaged. >> >> Everything not tested is broken, and so if you do things like that I am >> sure you will have problems. >> >> And nobody ever unloaded anything from Core. > > You must be joking right? In the mission you say "stable and small > core", but the numbers say something entirely different: PharoCore 1.0 > is 11 MB, PharoCore 1.1 is 14 MB, PharoCore 1.2 is 16 MB. I mentioned > it before in this list, but I already had to unload stuff in PharoCore > 1.1. Honestly, I don't really see the point of a PharoCore image if it > contains more and more not unloadable non-core code. > Size of the image comes in part from ever growing MC history. The only other big thing should be the Minimal Morphic code, which is in there temporarily. Else: People are welcome to help. We do what we do and then we do a release even if it is imperfect. Perfection is death, and delaying the release forever "because we could do better" will not mean that we do better, just that we don't release ever. Pharo 1.2 is *not* a goal in itself. It is just a snapshot on the way to a goal. Therefore it's just a mess that is tested for some month so it does not have any obvious bugs. Nothing else. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

5 4