- Pharo-dev - lists.pharo.org

[Pharo-project] Fwd: Issue 1298 in pharo: CrLfFileStream not properly initialized on Mac OS
by StÃ©phane Ducasse Dec. 5, 2009

Dec. 5, 2009

Begin forwarded message: > From: pharo(a)googlecode.com > Date: December 5, 2009 9:56:30 PM GMT+01:00 > To: stephane.ducasse(a)gmail.com > Subject: Re: Issue 1298 in pharo: CrLfFileStream not properly initialized on Mac OS > > > Comment #2 on issue 1298 by nicolas.cellier.aka.nice: CrLfFileStream not properly initialized on Mac OS > http://code.google.com/p/pharo/issues/detail?id=1298 > > 1) I don't like to see these getSystemAttribute: 1001 spreaded like a plague. We have > clear messages that perfectly insulate these cryptic secret codes. > 2) As I changed these getSystemAttribute: senders recently in trunk, I think I saw > more subtle things like testing for 'Darwin' or something... Aren't OS-X linefeed > based ? (I don't own a Mac...) > > -- > You received this message because you are listed in the owner > or CC fields of this issue, or because you starred this issue. > You may adjust your issue notification preferences at: > http://code.google.com/hosting/settings

1 0

[Pharo-project] Fwd: why OOP needs tails recursion article
by StÃ©phane Ducasse Dec. 5, 2009

Dec. 5, 2009

Begin forwarded message: > From: Eliot Miranda <eliot.miranda(a)gmail.com> > Date: December 5, 2009 9:55:14 PM GMT+01:00 > To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Subject: Re: why OOP needs tails recursion article > > Hi Steph, > > can you forward my response to the Pharo list? I guess I do need to join the Pharo list :/ > > Eliot (from under an avalanche of email) > > On Sat, Dec 5, 2009 at 12:32 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > On Sat, Dec 5, 2009 at 2:00 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > http://lambda-the-ultimate.org/node/3702 > > > I want to return to the implementation and optimization implications of this later. But Steele's post refers to William Cook's excellent paper On understanding data abstraction, revisited. Onward! Essays, 2009 ACM OOPSLA. SIGPLAN Notices 44, 10 (Oct. 2009), 557-572. There's a freely available draft version. The quote I want to emphasise is > > The extensibility of objects does not depend upon inheritance, but rather is an inherent property of object interfaces. > > The paper proves this point eloquently and concisely. The implication is that isKindOf: is <shout>BROKEN</shout>. In the absence of something better isSomeInterface to query whether an object implements some interface SomeInterface is acceptable. isKindOf: (and the horror I found the other day isKindOf:orKindOf: (you see why it exists and where it leads?)) is not and should be expunged. > > My weekend rant. > > best, > Eliot >

1 0

Re: [Pharo-project] asBit
by Ralph Boland Dec. 5, 2009

Dec. 5, 2009

> I currently writing a code which looks like: > > a := some numeric expression + (someBoolean ifTrue: [1] ifFalse: [0]). > > And i get somewhat tired repeating the same pattern in multiple places. > So, i thinking , maybe #asBit convenience method could be useful? > > True>>asBit > Â ^ 1 > False>>asBit > Â ^ 0 > > so, then, in case of need like above, we could write much shorter expressions: > a := some numeric expression + someBoolean asBit. > > And its much less error prone comparing to #ifTrue:ifFalse:, since i > found its relatively easy to make a mess (swapping 1 with 0), > especially, when you having negations in expression, because once you see: > > (someBoolean not ifTrue: [1] ifFalse: [0]) > > you always tempted to write it as: > > (someBoolean ifTrue: [0] ifFalse: [1]). > > or as: > > (someBoolean ifFalse: [1] ifTrue: [0]). > > but once you start playing with it, its very easy to shoot into own > feet if you are not careful. > > But if we could add #asBit, then we could write: > > someBoolean not asBit > > which is much more: > a) concise & cleaner > b) error proof > > > -- > Best regards, > Igor Stasenko AKA sig. I use "someBoolean card" for this where card stands for cardinality. The cardinality of false is 0 and of true is 1. Method "card" can also be used for other classes of object that have cardinal values associated with them. Regards, Ralph Boland -- Volume * Density = Mass. Volume / Density = Intelligence. The latter equation explains the essentially equal intelligence of men and woman and the capabilities of some commonly used operating systems.

1 0

[Pharo-project] How do I know which issues are resolved in each new release?
by Tim Mackinnon Dec. 5, 2009

Dec. 5, 2009

Hi guys - I noticed there was a new 9.11.4 release since buenos aires - and I got to wondering what issues have been resolved in it (as I am trying to follow Pharo by example - I am trying to test out features to see if they work as I progress through the material). Anyway - is there a list of issues fixed marked against each new version? I can see the list at: http://code.google.com/p/pharo/issues/list# - but it doesn't list any build numbers - just milestone 1.1? Tim

7 16

[Pharo-project] removing class instead of method
by StÃ©phane Ducasse Dec. 5, 2009

Dec. 5, 2009

Hi from time to time I get my class removed instead of a method. Is there a menu entry allowing to do that on the **method** menu items. Because this is really annoying. Stef

2 4

[Pharo-project] christmas coding parties?
by StÃ©phane Ducasse Dec. 5, 2009

Dec. 5, 2009

Hi all I would like to organize a couple of coding parties around christmas. The 18 of december? is one possibility (even if I can only start at 11h). So if some of you are close to lille during holidays we could have fun coding together. I would like to organize a moose day too. I want to code what I have in mind with CAnalyzer and mondrian. Stef

5 16

[Pharo-project] why OOP needs tails recursion article
by StÃ©phane Ducasse Dec. 5, 2009

Dec. 5, 2009

http://lambda-the-ultimate.org/node/3702

3 2

[Pharo-project] file encodings
by Tudor Girba Dec. 5, 2009

Dec. 5, 2009

Hi, I know that there was a long discussion regarding opening of files, but I did not see a resolution. I would like to be able to read files regardless of the encoding. I am using this code: (CrLfFileStream readOnlyFileNamed: fullPath) contentsOfEntireFile" but I get an error when I reach a file in Latin 1 (ISO-8859-1). How can I safely deal with this issue without getting hurt? Cheers, Doru -- www.tudorgirba.com "When people care, great things can happen."

6 10

Dec. 5, 2009

11071 ----- - Issue 1545: cmdDotEnabled preferences is not working - Issue 1353: make #keys answer an Array rather than a Set Part One http://code.google.com/p/pharo/issues/detail?id=1353 - Issue 972: PackageOrganizer is full of wrong packageinfo ScriptLoader new cleanUpPackageOrganizer - Issue 1354: making #classVarNames a sorted Array http://code.google.com/p/pharo/issues/detail?id=1354 Thanks Lukas, Nicolas and Alain This makes me think that I could produce more, anyway..... Stef

1 0

Dec. 5, 2009

Nicolas I was discussing with lukas and we would be interested to get your changes to dictionary keys (Ihope that this icorrect since I'm dead) We would like to integrate your changes. Do you have a basis that we could work? Else we can just try in the image directly. Stef

8 25