I reported it for 3.0 here: https://code.google.com/p/pharo/issues/detail?id=7619
Cheers, Martin On Wed, Feb 27, 2013 at 11:35 AM, [email protected] <[email protected]> wrote: > One great things about Pharo is the ability to nuke old crap. > > It feels good :-) > > Phil > > 2013/2/27 Sven Van Caekenberghe <[email protected]>: >> >> On 27 Feb 2013, at 11:19, Martin Dias <[email protected]> wrote: >> >>> Hi >>> >>> I discovered this protocol in String hierarchy. Are you familiar with it? >>> >>> The method comment of #fromPacked: is: >>> "Convert from a longinteger to a String of length 4." >>> >>> The only sender in Pharo 2.0 is MethodFinder. For WideString, it does not >>> work. >>> >>> In examples: >>> >>> ByteString fromPacked: 'text' asPacked. ---> 'text' >>> ByteString fromPacked: 'martin' asPacked. ---> 'rtin' >>> WideString fromPacked: ('text' asWideString asPacked). ---> error >>> >>> >>> >>> WideString>>asPacked can be easily fixed adding an explicit return to >>> the calculation (it's now implicitly returning self). >>> >>> But... it only encodes one letter: >>> >>> WideString fromPacked: 'martin' asWideString asPacked ---> 'n' >>> >>> >>> I checked that in Squeak 4.3 there are not senders too. >>> >>> So... Should we fix the WideString implementation, or directly remove >>> this protocol? >>> >>> Martin >> >> It might have something to do with pre Mac OS X days, Mac creator/type codes. >> >> Unless this follows some open standard with a spec, I would say nuke it. >> >> Doing something like this without specifying encoding strikes me as >> dangerous. >> >> Sven >> >> -- >> Sven Van Caekenberghe >> http://stfx.eu >> Smalltalk is the Red Pill >> >> >
