- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 2488 in pharo: LargeInteger ln overflows

by pharo＠googlecode.com

Updates: Status: Closed Labels: Milestone-1.3 Comment #6 on issue 2488 by marcus.d...(a)gmail.com: LargeInteger ln overflows http://code.google.com/p/pharo/issues/detail?id=2488 in 13106

March 23, 2011

Re: [Pharo-project] Issue 3844 in pharo: Utilities is in StartupList

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3844 by marcus.d...(a)gmail.com: Utilities is in StartupList http://code.google.com/p/pharo/issues/detail?id=3844 in 13106

March 23, 2011

Re: [Pharo-project] String>>#base64Encoded

by Tony Fleig

In other language environments I have seen base64 encoders where the line break is optional, or where a maximum line length can be specified. In Smalltalk it might look line: String>>#base64Encoded String>>#base64EncodedWithLineBreaks or String>>#base64EncodedMaxLineLength: TF On Mon, Mar 21, 2011 at 11:45 PM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > > On 21 Mar 2011, at 21:52, StÃ©phane Ducasse wrote: > > > On Mar 21, 2011, at 9:42 PM, Sven Van Caekenberghe wrote: > > > >> Hi, > >> > >> It took me quite some time today to figure this out and it might be > relevant for others too: > >> > >> it turns out that String>>#base64Encoded introduces newlines which you > definitively do not want when doing Basic HTTP Encoding for example. The > tricky part is that it works when you stay below a certain length. > > > > when would it makes sense? > > Base64 encoding ( http://en.wikipedia.org/wiki/Base64 ) is a techique to > encode binary data in ASCII strings using a radix 64 representation. It came > from the early days of the internet where is was used to encode binary stuff > in mail messages (part of MIME encoding). For these usages, line breaks make > sense, since some email client break lines themselves, and by preformatting > you prevent that, for example: > > (Base64MimeConverter > mimeEncode: (ZnClient get: ' > http://www.pharo-project.org/favicon.ico') entity readStream > multiLine: true) contents > > 'AAABAAEAEBAAAAEAIABoBAAAFgAAACgAAAAQAAAAIAAAAAEAIAAAAAAAAAAAABMLAAATCwAA > AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA0K1+/+2tF//lpRj/0J1F/86x > kP8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADQso7/ > 1Zw1/+ekF//koBf/zZdF/wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA > AAAAAAAAAAAAAAAAAADLrIr/yI05/9SLG//UvKP/AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA > AAAAAAAAAAAAAAAA3s2//8qrjf8AAAAAAAAAAAAAAADClmr/28m4/wAAAAAAAAAAAAAAAAAA > AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACpayz/rH1S/9K9q/8AAAAAAAAAAAAAAAAAAAAA > AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAxKeP/4lWLv9+Tiz/oXtc/97P > xf8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADYxrj/ > oX1j/2RBNP+QbFT/AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA > AAC6m4H/1MGz/+7m4v/Ltqb/tJR3/wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA > AAAAAAAAAAAAAAAAsJWF/1tHVf+qkIH/4tTL/wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA > AAAAAAAAAAAAAAAAAAAAAAAAAAAAANG8rf9GPGj/IiJn/19MYP/Mt6n/AAAAAAAAAAAAAAAA > AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAANXEuP9NQGj/IiiB/youf/8NFnb/Qztx/9PC > t/8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADczcL/mIGA/y8ziP8nMZj/ > GSGF/4l2hP/Tw7n/AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMy4 > q/8pMZj/JzKi/yUxov+znJb/AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA > AAAAAAAAAADezsT/d3Om/1dt0f9cZrz/v6mf/wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA > AAAAAAAAAAAAAAAAAAAAAAAAAAAAAJqapP+i3f//iazZ/9/Pwv8AAAAAAAAAAAAAAAAAAAAA > AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADBqIv/lYps/7Caev8AAAAAAAAAAAAA > AAAAAAAA/g8AAP8H8L//wwAA/nMAAP8fNcL/BwAA/4cAAP8HAAD/DwAA/wc4FP4DAAD+AwAA > /wf///8H////hzp0/48AAA==' > > Base64 encoding is also used a lot in cryptography to encode binary data > like hashes or even for silly obfuscation. For example, in HTTP, Basic > Authentication is a defined as a HTTP header called 'Authorization' with as > value 'Basic' <space> <credentials> where credentials is obtained by Base64 > encoding <username>:<password>. > > ZnRequest>>#setBasicAuthenticationUsername: username password: password > self headers > at: 'Authorization' > put: 'Basic ', (ZnUtils encodeBase64: (username, ':', > password)) > > ZnUtils class>>#encodeBase64: string > ^ (Base64MimeConverter mimeEncode: string readStream multiLine: > false) contents > > Here you don't want line breaks since it would break the common assumption > that a header is a single line (technically, multiline headers do exist, but > that is another story). > > Now, as long as the input string is below 55 characters in length, no line > breaks will be introduced. In code (assuming no line line breaks will be > introduced by our email clients or the mailing list software inbetween; > re-execute in a workspace if necessary): > > (Base64MimeConverter > mimeEncode: ((String new: 54) atAllPut: $A) readStream > multiLine: true) contents > > 'QUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFB' > > (Base64MimeConverter > mimeEncode: ((String new: 54) atAllPut: $A) readStream > multiLine: false) contents > > 'QUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFB' > > (Base64MimeConverter > mimeEncode: ((String new: 55) atAllPut: $A) readStream > multiLine: true) contents > > 'QUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFB > QQ==' > > (Base64MimeConverter > mimeEncode: ((String new: 55) atAllPut: $A) readStream > multiLine: false) contents > > > 'QUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQQ==' > > Please note, this is not a bug, just a gotcha that can go unnoticed for > quite some time. > > Sven > > PS: Base64 decoding is clever enough to transparently deal with line > breaks. > > >> This can easily be solved by invoking Base64MimeConvertor with the > #mimeEncode: <string> multiLine: false > >> > >> Zinc HTTP Components now does this consistently through ZnUtils > class>>#encodeBase64: > >> > >> Sven > > >

March 23, 2011

[Pharo-project] Issue 3853 in pharo: Integrate image-side changes to use new primitive to disable module loading

by pharo＠googlecode.com

Status: FixProposed Owner: siguc...(a)gmail.com Labels: Milestone-1.3 Type-Patch New issue 3853 by siguc...(a)gmail.com: Integrate image-side changes to use new primitive to disable module loading http://code.google.com/p/pharo/issues/detail?id=3853 see http://code.google.com/p/cog/issues/detail?id=13

March 23, 2011

[Pharo-project] [TODO 1.2] TODO list for releasing Pharo Full 1.2

by Marcus Denker

http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2-DevImage 1. 1.2 Build is broken 2. 1.2 Config needs to load latest code from OB Repository (or not. Maybe we should just release 1.2.1 and do that in 1.2.2) maybe these we push to 1.2.2: 3. Omnibrowser's an extra horizontal scrollbar 4. In OB: Text in comment pane of Browser uses syntax highlighting 5. Update Hudson One-Click build files for 1.2 Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 23, 2011

[Pharo-project] Issue 3852 in pharo: 1.2 Build is broken

by pharo＠googlecode.com

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.2-DevImage New issue 3852 by marcus.d...(a)gmail.com: 1.2 Build is broken http://code.google.com/p/pharo/issues/detail?id=3852 DuplicatedVariableError: stylingActive is already defined in Workspace Not clear why it suddenly tries to load different code.

March 23, 2011

Re: [Pharo-project] Pharo 1.2 red again

by Marcus Denker

On Mar 23, 2011, at 12:52 PM, Torsten Bergmann wrote: > Pharo 1.2 is red again! > > DuplicatedVariableError: stylingActive is already defined in Workspace > > https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/195/ We really need to make sure that the config does not load code if we don't explicitly say so. So what code was changed? Why was it loaded? -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 23, 2011

[Pharo-project] Pharo 1.2 red again

by Torsten Bergmann

Pharo 1.2 is red again! DuplicatedVariableError: stylingActive is already defined in Workspace https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/195/ -- NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://www.gmx.net/de/go/freephone

March 23, 2011

Re: [Pharo-project] test crashing the cog vm

by Stefan Marr

On 22 Mar 2011, at 19:00, StÃ©phane Ducasse wrote: > Can you explain rapidly register-case byte code? And for those who still wonder why that might be useful, an article titled: 'Virtual Machine Showdown: Stack Versus Registers' @article{1328197, address = {New York, NY, USA}, author = {Yunhe Shi and Kevin Casey and M. Anton Ertl and David Gregg}, interhash = {5fbfc20a2129ec1897d295cace8e3595}, intrahash = {e329d8905cc5c93be9782963125d9644}, journal = {ACM Trans. Archit. Code Optim.}, number = 4, pages = {1--36}, publisher = {ACM}, title = {Virtual Machine Showdown: Stack Versus Registers}, url = {http://portal.acm.org/citation.cfm?id=1328195.1328197}, volume = 4, year = 2008, added-at = {2008-09-03T21:02:27.000+0200}, issn = {1544-3566}, description = {Virtual machine showdown}, biburl = {http://www.bibsonomy.org/bibtex/2e329d8905cc5c93be9782963125d9644/gron}, doi = {http://doi.acm.org/10.1145/1328195.1328197} } -- 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

March 23, 2011

[Pharo-project] Magritte extension dealing with graphics

by StÃ©phane Ducasse

Hi did one of you extended magritte to deal with graphics (Form, InageMorph...)? Stef

March 23, 2011