- Pharo-dev - lists.pharo.org

[Pharo-project] Issue 3978 in pharo: Undeclared vars in MorphTreeMorph
by pharo＠googlecode.com April 9, 2011

April 9, 2011

Status: Accepted Owner: marcus.d...@gmail.com Labels: Milestone-1.3 New issue 3978 by marcus.d...@gmail.com: Undeclared vars in MorphTreeMorph http://code.google.com/p/pharo/issues/detail?id=3978 - searchedElement (it has accessors) - lastKeystrokeTime - lastKeystrokes - lastSelection

1 1

[Pharo-project] [update 1.3] #13138
by Marcus Denker April 9, 2011

April 9, 2011

13138 ----- Issue 3849: ExternalSettings should be cleaned Issue 2559: Senders of #ifNotNil: do not show -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] Issue 2559 in pharo: Senders of #ifNotNil: do not show
by pharo＠googlecode.com April 9, 2011

April 9, 2011

Comment #2 on issue 2559 by marcus.d...@gmail.com: Senders of #ifNotNil: do not show http://code.google.com/p/pharo/issues/detail?id=2559 Issue 2911 has been merged into this issue.

1 11

[Pharo-project] Issue 3849 in pharo: ExternalSettings should be cleaned
by pharo＠googlecode.com April 9, 2011

April 9, 2011

Status: Accepted Owner: marcus.d...@gmail.com New issue 3849 by marcus.d...@gmail.com: ExternalSettings should be cleaned http://code.google.com/p/pharo/issues/detail?id=3849 When Issue 3638 is closed, MC will be the only client of ExternalSettings. ExternalSettings was a Preferences Framework that was only used by three clients: etoys, setting http proxy and MC. I vote for removing it.

1 3

[Pharo-project] Issue 3692 in pharo: Default line-end convention fix
by pharo＠googlecode.com April 9, 2011

April 9, 2011

Status: Accepted Owner: siguc...@gmail.com New issue 3692 by siguc...@gmail.com: Default line-end convention fix http://code.google.com/p/pharo/issues/detail?id=3692 Multibyte filestream guess about line endings was apparently wrong. Should use CR for MacOS and LF for rest unixes, not vise verse. Attachments: fix-line-ends.1.cs 678 bytes

1 7

Re: [Pharo-project] Have started an independent developer activity - Thank you
by Marcus Denker April 9, 2011

April 9, 2011

On Apr 9, 2011, at 9:34 AM, laurent laffont wrote: > Hi, > > I discovered Smalltalk and Pharo almost three years ago and just after read Chad Fowler book "Passionate Programmer" (1st edition title was "My job went to India"). These have changed my developer life, how I perceive software and that great technology is fun, people doing it more. You're a cool community and I'm proud to be there. > > Now I've started an aside (paid :) independent developer activity thanks to a cool guy. That would not be possible without all the stuff I learn every day from the community and the urge to continue you give me. > > Each time I've made a step forward (open a blog, write ProfStef, fix bugs, create PharoCasts) I've been amazed that the generated effects were those described in Passionate Programmer (go read it !) The last chapter is "Go independent" so now I need the sequel ;) > So we can add an entry to the "companies using pharo" soon, I hope! http://www.pharo-project.org/about/success-stories -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

Re: [Pharo-project] Unexpected behavior of roundTo:
by Marcus Denker April 9, 2011

April 9, 2011

On Apr 9, 2011, at 9:09 AM, Andres Valloud wrote: > At the end of the day, we still insist on expecting there won't be loss of information just because we wrote a decimal print string for a binary floating point number. One can get offended or irritated all one wants, but the reality of the situation won't change. > > I think the real solution to these "problems" is to implement decimal floating point as per IEEE-754/2008. \\ The MPFR lib seems to me (as far as I understand) is inspired by IEEE 754 <SNIP> MPFR is a portable library written in C for arbitrary precision arithmetic on floating-point numbers. It is based on the GNU MP library. It aims to provide a class of floating-point numbers with precise semantics. The main characteristics of MPFR, which make it differ from most arbitrary precision floating-point software tools, are: â¢ the MPFR code is portable, i.e., the result of any operation does not depend on the machine word size mp_bits_per_limb (64 on most current processors); â¢ the precision in bits can be set exactly to any valid value for each variable (including very small precision); â¢ MPFR provides the four rounding modes from the IEEE 754-1985 standard, plus away-from-zero, as well as for basic operations as for other mathematical functions. .... The following five rounding modes are supported: â¢ MPFR_RNDN: round to nearest (roundTiesToEven in IEEE 754-2008), â¢ MPFR_RNDZ: round toward zero (roundTowardZero in IEEE 754-2008), â¢ MPFR_RNDU: round toward plus infinity (roundTowardPositive in IEEE 754-2008), â¢ MPFR_RNDD: round toward minus infinity (roundTowardNegative in IEEE 754-2008), â¢ MPFR_RNDA: round away from zero (experimental). The âround to nearestâ mode works as in the IEEE 754 standard: in case the number to be rounded lies exactly in the middle of two representable numbers, it is rounded to the one with the least significant bit set to zero. For example, the number 2.5, which is represented by (10.1) in binary, is rounded to (10.0)=2 with a precision of two bits, and not to (11.0)=3. This rule avoids the drift phenomenon mentioned by Knuth in volume 2 of The Art of Computer Programming (Section 4.2.2). </SNIP> > Then you can write something like 1.2345 and know for a fact the number represented is *exactly* 1.2345. At least one VisualWorks platform already supports decimal floating point in hardware (IBM's POWER line). C99 extensions exist at least in draft form to extend C so that it supports decimal floating point. IBM has released a GPL library in ANSI C that implements the feature. I am not sure what is the deal with the license and if you can e.g.: interface to it without making your whole Smalltalk GPL. > MPFR is LGPL, so linking that in the VM or using it via FFI is no problem license wise. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

[Pharo-project] Issue 3975 in pharo: References to ivars shortcut
by pharo＠googlecode.com April 9, 2011

April 9, 2011

Status: FixToInclude Owner: siguc...@gmail.com Labels: Milestone-1.3 Type-Patch New issue 3975 by siguc...@gmail.com: References to ivars shortcut http://code.google.com/p/pharo/issues/detail?id=3975 In editor you can just select ivar name and then press cmd-shift-N to see all references to it, instead of using browser button. Attachments: ivarrefs.1.cs 684 bytes

1 2

Re: [Pharo-project] [Pharo-users] 1.2.1 Windows no-no
by Mariano Martinez Peck April 9, 2011

April 9, 2011

On Sat, Apr 9, 2011 at 7:07 PM, Robert Shiplett <grshiplett(a)gmail.com>wrote: > I just inspected the pharo LNK file of my new > > C:\Pharo-1.2.1-CogOneClick.app > > and it is set to start in > > > "C:\Documents and Settings\Administrator\Desktop\OneClick.app" > > > WRONG! > > I am logged in as another user and not as Administrator ( which on XP > I only enter from Safe Mode ) > > > Pharo might be okay using my > > C:\Documents and Settings\Owner\Local Settings\Application Data > > I have reset the LNK as starting in > > C:\Pharo-1.2.1-CogOneClick.app\Contents\Resources > > and reset the TARGET to > > C:\Pharo-1.2.1-CogOneClick.app\Contents\Windows\Squeak.exe pharo.image > > > Some Windows users would not be amused to see this Administrator ... > as all too often spyware goes where it does not belong ... especially > on Corp desktops. > Can you please submit an issue with that please? Check these threads: http://forum.world.st/template/NamlServlet.jtp?macro=search_page&node=12948… > > If we use an sh for Linux, why can't we use a simple BAT for Windows? > > Are you aware of the Windows installer ? -- Mariano http://marianopeck.wordpress.com

1 0

[Pharo-project] TestResource bug?
by Guillermo Polito April 9, 2011

April 9, 2011

Hi! I'm using pharo 1.2 and I've found a little problem in here TestResource>>makeAvailable "This method must be the _only_ way to set a notNil value for the unique instance (current). First, obtain a candidate instance and set current to a notNil placeholder (any notNil object not an instance of me would do; this version uses false). Next, check any subordinate resources needed by this resource. Lastly, setUp the candidate and put it in current if it is available, ensuring that it is torn down otherwise." | candidate | * current := false.* candidate := self new. self resources do: [:each | each availableFor: candidate]. [candidate setUp. candidate isAvailable ifTrue: [current := candidate]] ensure: [current == candidate ifFalse: [candidate tearDown]] And everywhere in the class, the check over the current class instance var is done like current isNil ifTrue: .... So once that var is initialized, but the makeAvailable fails, it always fails... Is this a bug or i'm doing a mistake? Shouldn't *current := false be changed *be changed by *current := nil. *??* *Thanks! Guille

1 0