- Pharo-dev - lists.pharo.org

Fwd: Pharo and scaled decimals
by StÃ©phane Ducasse July 8, 2013

July 8, 2013

It seems that we never integrate this change (there was not bug entry :)). I will open a bug entry if not. Stef Begin forwarded message: > From: David Gorisek <david.gorisek(a)e-racuni.com> > To: pharo-project(a)lists.gforge.inria.fr > Cc: > Date: Wed, 13 Mar 2013 22:24:04 +0100 > Subject: Pharo and scaled decimals > Hello all, > > I am testing Pharo and I have noticed that the Pharo compiler does not treat ScaledDecimals the same way they are treated in other Smalltalk dialects (e.g. VW, VAST, Dolphin, STX, etc.). > > For example the following is a valid code representing an instance of ScaledDecimal/FixedPoint in all other dialect. > > 1.0s + 2.0s > > In Phare the code above wont compile, it has to be written as: > > 1.0s1 + 2.0s1 > > So I have made the following quick change to make Pharo compatible with other Smalltalk dialects. Maybe this change could be included in the next version of Pharo? > > SqNumberParser>>#readScale > "read the scale if any (stored in instVar). > Answer true if found, answer false if none. > If scale letter is not followed by a digit, this is not considered as an error. > Scales are always read in base 10, though i do not see why..." > > scale := 0. > sourceStream atEnd > ifTrue: [ ^ false ]. > (sourceStream peekFor: $s) > ifFalse: [ ^ false ]. > scale := self nextUnsignedIntegerOrNilBase: 10. > scale > ifNil: [ > scale := 0. > (sourceStream peek ifNil: [false] ifNotNil: [ :nextChar | nextChar isLetter]) > ifTrue: [ > sourceStream skip: -1. "ungobble the s" > ^ false ] > ifFalse: [ ^ true ] ]. > ^ true

2 2

YAML Parser?
by Stefan Marr July 8, 2013

July 8, 2013

Hi: Is anyone aware of a YAML parser that's compatible with Pharo 1.4 and 2.0? (http://yaml.org/) I am using only the most basic features, so, it wouldn't need to be feature complete. Thanks Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

3 2

NeoCSV doc is now on Gutenberg :)
by StÃ©phane Ducasse July 8, 2013

July 8, 2013

Hi sven I converted and modified the documentation you did. I love reading documentation :) This is still draft because some examples are missing but we have a solid basis. Stef

3 3

Pharo2.0 unti test oddity
by Dale K. Henrichs July 8, 2013

July 8, 2013

I'm running this test in Pharo2.0 using TestRunner. Can someone explain to me why this test would PASS while: - the debugger is not brought up - the description of the exception _is_ displayed in the transcript Error reading repository properties (.filetree): /Users/dhenrich/Pharo2.0/Pharo2.0-portable.app/Contents/Resources/temp/repo :: Error: end of input expected Here's the test method: testWrite [ | packageName version versionInfo | #('CCC') do: [ :pn | self deny: (self hasPackage: pn) ]. packageName := 'CCC'. Gofer new disablePackageCache; repository: (self getTestRepository: 'issue33'); package: packageName; load. self validateTimestamp: 'dkh 11/2/1954 16:15'. #('CCC') do: [ :pn | versionInfo := (MCWorkingCopy allManagers detect: [ :wc | wc packageName = pn ]) ancestors first. version := (self getTestRepository: 'issue33') versionWithInfo: versionInfo. (self getTestRepository: 'empty') storeVersion: version ] ] on: Error do: [:ex | self halt. Transcript cr; show: ex description. ex pass] The test passes with flying colors if I run it from a workspace as well: MCFileTreeIssue33Test debug: #testWrite I'd kinda like to debug this test failure:( Using Pharo2.0-20610 from Pharo2.0-portable download (in the last day or two). Dale

2 4

Looking for ..
by StÃ©phane Ducasse July 7, 2013

July 7, 2013

Hi guys I would like to build a list bachelor projects that we can advertise. I would like to build a really web site just a text + a paragraph and a list of items each item should present a simple page Ideally I would like that people can edit their own project. should I use a git repo and use marddown? Stef

2 1

STON on gutenberg
by StÃ©phane Ducasse July 7, 2013

July 7, 2013

Hi Since I wanted to really read it again I converted and enhanced the documentation of STON. Soon available on jenkins and already on github. Stef

3 4

Jenkins message question
by StÃ©phane Ducasse July 6, 2013

July 6, 2013

Hi guys for the Pharo for the entreprise book I get on the web: ' #103 (pendingâWaiting for next available executor) do you have an idea about what it means Stef

2 2

FileReference(Object)>>doesNotUnderstand: #other
by Andrei Vasile Chis July 6, 2013

July 6, 2013

Hi, This code fails in both Pharo 2 and Pharo 3: 'FileSystem disk root children sorted' It throws this exception: FileReference(Object)>>doesNotUnderstand: #other Andrei

2 2

NativeBoost with no access to sources
by Goubier Thierry July 6, 2013

July 6, 2013

Is there something against that ? It seems as if NB is used to check file existence / isReadable, then, upon startup, the vm is unable to open the changes file and all NB calls becomes incorrect. Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

5 22

[Issue tracker] Please have a look at your issues!
by Marcus Denker July 6, 2013

July 6, 2013

Hi, We should do a pass over all issues. e.g. -> is your bug still relevant? -> if you submitted a fix, maybe the bug status is wrong and therefore nobody looked at it? -> if you added a verbal description of how to fix something, consider submitting code in addition (people have just no idea how much easier it is to deal with machine readable code than half-a-page of proseâ¦) -> You where involved in a discussion about a bug. So now go trough it and summarize: What is the next *action* that needs to be done to close the issue? You can get a list of *all* open issues: https://pharo.fogbugz.com/f/filters/33/All-Opened or just the ones for 2.0: https://pharo.fogbugz.com/f/filters/8/2-0-Work-Needed and 3.0: https://pharo.fogbugz.com/f/filters/37/3-0-Work-Needed For the 2.0/3.0 issues, we should decide: are they really of a kind that they need to fixed before we can release? (in 2.0: do we really need to back port? or is it enough to fix in 3.0?) Marcus

5 7