- Pharo-dev - lists.pharo.org

[Pharo-project] A process point: how to submit your changes
by StÃ©phane Ducasse June 14, 2009

June 14, 2009

hi guys When you submit a fix do not merge it with items in the inbox. Why? because it forces us to - find the slice that defined the packages you merged with - integrate this fix too. So it binds fixes together and this is not good. For example we cannot integrate a simple fix ( if it merged with a more complex one) without thinking too much. Stef

1 0

[Pharo-project] Fixes for Numbers are ready (toward ANSI)
by Nicolas Cellier June 13, 2009

June 13, 2009

I cumulated the changes in this order: http://code.google.com/p/pharo/issues/list?id=874 PharoInbox/SLICE-Mantis6985-Issue874-Integer-bitAt-nice.1 add Integer #bitAt: http://code.google.com/p/pharo/issues/list?id=875 PharoIbox/SLICE-Mantis6601-Issue875-Float-hash-nice.1 fix Float hash http://code.google.com/p/pharo/issues/list?id=876 PharoInbox/SLICE-Mantis3374-Issue876-Arithmetic-Equality-transitive-Part1-nice.1 PharoInbox/SLICE-Mantis3374-Issue876-Arithmetic-Equality-transitive-Part2-nice.1 fix number equal transitivity (and further change Fraction hash) http://code.google.com/p/pharo/issues/detail?id=681 PharoInbox/SLICE-Mantis6982-Issue681-Number-readFrom-nice.1 connect SqNumberParser in Number readFrom: (with backward compatibility) http://code.google.com/p/pharo/issues/list?id=879 PharoInbox/SLICE-Issue879-ANSI-FloatCharacterization-nice.1 add ANSI Float Characterization Please review :) Nicolas

4 7

[Pharo-project] about FLoatArrays isZero
by StÃ©phane Ducasse June 13, 2009

June 13, 2009

isZero on collection does not make sense so it was deprecated now some tests like are breaking 3.0 / (FloatArray with: 2.0) = (FloatArray with: 1.5) so ? Stef

3 5

[Pharo-project] Issue 67 and CrLfFileStream
by Norbert Hartl June 13, 2009

June 13, 2009

I've fixed issue 67. SLICE is in PharoInbox. While looking at the classes I found some things. CrLfFileStream is somehow obsolete. Its new class method creates a MultiByteFileStream. The code in both classes is doubled. I didn't check but I would expect it is close to all of the code. This is again a question if we are willing to break back- ward compatibility. I would opt for removing the class completely. If not I would change MultiByteFileStream in a way that it inherits from CrLfFileStream. This way we could at least remove the doubled code/methods. Or does anybody know reasons why the one or other isn't feasible to do? Furthermore I would remove the handling of line endings with symbols. These could just be the strings they contain. String cr, String lf and String crlf all exist. Using this instead of the symbols we could remove half of the class variables and get rid of the LineEndStrings dictionary. What do you think? And could someone please review my changes. I don't have a Mac. Well, the difference is only noticable if you have a system < 10. Norbert

2 3

[Pharo-project] package extension question
by StÃ©phane Ducasse June 13, 2009

June 13, 2009

Hi Apparently some class extensions category are stored in lowercase, and this makes difficult to find a package given a method category. methodCategoryPrefix ^ methodCategoryPrefix ifNil: [methodCategoryPrefix := '*', self packageName asLowercase] I would be nice to make sure that we can go from a package to its class extensions and from the class extensions to its package. Now using asLowercase breaks this dual relationship. What do you think? Ideally I would like to fix all the package extensions to reflect exactly their package name and also change the code above to ensure that we get a real bijection. Stef

1 0

[Pharo-project] [update] #10334
by Marcus Denker June 13, 2009

June 13, 2009

#10334 ====== Issue 877: Collection>>isZero use deprecatedDescrition: instead of deprecated Issue 686: Remove dice methods in Random Issue 631: API Consistency on MIMEDocument -- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile

3 2

[Pharo-project] Issue Fixing Process
by Gabriel Cotelli June 13, 2009

June 13, 2009

What is the process to fix an issue? There's someone coordinating who is working on what? Or just I take an issue from the list and If I can write a fix post this to inbox? As a start point I will run the test cases and see if I can fix the failing... (Issue 409). Regards, Gabriel

3 4

[Pharo-project] [update] #10338
by Marcus Denker June 13, 2009

June 13, 2009

#10338 ====== Issue 66: 7116 setHeadingFix-wiz-1 -- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile

1 0

[Pharo-project] Issue 66 fixed
by Norbert Hartl June 13, 2009

June 13, 2009

Hi, I'be fixed Issue 66. It was basically renaming of test methods from ...test to test... This activated new tests that were there but hidden :) It is in PharoInbox Tests-Bugs-norbert_hartl.2 Norbert

1 0

[Pharo-project] New Pharo based on core 10318 with antialiased fonts
by Damien Cassou June 13, 2009

June 13, 2009

New Pharo: http://pharo-project.org/download -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

14 43