Pharo compatibility

> As I threatened a while back, I've started up a "Pharo shim" - a
> package that adds to a Squeak image those messages necessary to get
> interesting Pharo projects working in Squeak:
>
> http://www.squeaksource.com/PharoCompatibility
>
> At the moment "interesting projects" means "PetitParser", and so the
> shim merely contains Symbol >> #isBinary.
>
> Going forwards, as I find other bits necessary - my upcoming
> Helvetia/LanguageBoxes work will no doubt uncover bits and pieces -
> I'll add to Pharo-Compatibility.
>
> I expect some bits to make their way into trunk, and we can regard
> Pharo-Compatibility as a proving ground of sorts.
>
> frank
>
>

> Every one knows that messages in Smalltalk syntax can be
>  - unary
>  - binary
>  - keyword
> Unsurprisingly, there are corresponding methods implemented in
> Symbol... isUnary, isKeyword and...
> isInfix
> "Answer whether the receiver is an infix message selector."
> ^ self precedence = 2
> Hmm, the name was surprising!
>
> It would not hurt me to see isBinary integrated in trunk and replacing
> the isInfix sends...

> Maybe the purpose was to avoid polymorphism with Stream>>isBinary ?
>
> Nicolas
>
> 2011/9/3 Frank Shearar <[hidden email]>:
>> As I threatened a while back, I've started up a "Pharo shim" - a
>> package that adds to a Squeak image those messages necessary to get
>> interesting Pharo projects working in Squeak:
>>
>> http://www.squeaksource.com/PharoCompatibility
>>
>> At the moment "interesting projects" means "PetitParser", and so the
>> shim merely contains Symbol >> #isBinary.
>>
>> Going forwards, as I find other bits necessary - my upcoming
>> Helvetia/LanguageBoxes work will no doubt uncover bits and pieces -
>> I'll add to Pharo-Compatibility.
>>
>> I expect some bits to make their way into trunk, and we can regard
>> Pharo-Compatibility as a proving ground of sorts.
>>
>> frank
>>
>>
>
>