Issue 5058 in pharo: Number padding fails for negative numbers

Status: Accepted
Owner: [hidden email]
Labels: Type-Bug

New issue 5058 by [hidden email]: Number padding fails for negative  
numbers
http://code.google.com/p/pharo/issues/detail?id=5058

-5 printPaddedWith: $0 to: 3 '0-5'
-5.1 printPaddedWith: $0 to: 3.3 '0-5.100'
-5 printPaddedWith: $0 to: 3 base: 10 '0-5'
-5 asTwoCharacterString '-5'

For #asTwoCharacterString, is that used? It might be useful if it was  
#asTwoDigitString -5 -> -05...


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #2 on issue 5058 by [hidden email]: Number padding fails for  
negative numbers
http://code.google.com/p/pharo/issues/detail?id=5058

The first three are easy, just put the dash in the right place:
-5 printPaddedWith: $0 to: 3
     '-05' instead of '0-5'
       
-5.1 printPaddedWith: $0 to: 3.3
     '0-5.100' instead of '-05.100'
       
-5 printPaddedWith: $0 to: 3 base: 10
         '0-5' instead of '-05'

For #asTwoCharacterString, the only sender in the image is the MailMessage  
fix I just made, which I can change. If no one can think of a use case, I  
say we deprecate it.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Labels: -Milestone-1.4

Comment #3 on issue 5058 by [hidden email]: Number padding fails for  
negative numbers
http://code.google.com/p/pharo/issues/detail?id=5058

(No comment was entered for this change.)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Closed

Comment #4 on issue 5058 by [hidden email]: Number padding fails for  
negative numbers
http://code.google.com/p/pharo/issues/detail?id=5058

With Pharo 2.0 now beta, time has come to review bug reports that have not  
seen any activity in 2012.
To keep the amount of issues managable, we close reports that have not  
drawn any attention for over one
year.

The reporter (and thus owner) of the issue should:

  -> check the issue in 2.0. Is it still relevant?
  -> If yes, just add a note to the report and we will be opened again.


As your issue has not seen any attention for over a year, please consider  
to give more information.
A good idea can be to send a mail to the mailinglist to get other people to  
help fixing the bug or
implementing an improvement.



_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker