[Pharo-project] ClassBoxes... bitrotted, or usable?

Jan Vrany jan.vrany at fit.cvut.cz
Tue Jun 5 03:52:25 EDT 2012


On 04/06/12 22:56, Alexandre Bergel wrote:
> This was the implementation in Modular Smalltalk if I remember correctly.
>
> In plain Smalltalk you send a message named #msg and the lookup gives you a compile method.
> In Modular Smalltalk, there is an intermediary step: #msg ->  #Namespace.msg ->  compile method
>

I see. What I do not see is how to achieve this without a cost at 
runtime. Given that it should support imports. Without imports, SNs are
pretty much useless :-)

Jan



> Alexandre
>
> On Jun 4, 2012, at 8:34 AM, Jan Vrany wrote:
>
>> Hi
>>
>>
>> - having a class Selector that get evaluated into a symbol. You can then achieved selector namespaces, which does not incur a cost at execution.
>>
>> I do not understand the idea. Could you give an example?
>>
>>
>> Cheers, Jan
>>
>>
>>
>>>
>>> Cheers,
>>> Alexandre
>>>
>>>
>>> On Jun 1, 2012, at 10:55 AM, Frank Shearar wrote:
>>>
>>>> I mused with a colleague about how I'd like to see "lexically scoped
>>>> monkey patching", and he pointed me to some guys that want to add that
>>>> to Ruby (http://timelessrepo.com/refinements-in-ruby). Note the
>>>> inspiration for their work: ClassBoxes!
>>>> (http://scg.unibe.ch/research/classboxes)
>>>>
>>>> I remember reading the paper years ago, and started working through it
>>>> again now. Something that's not clear to me is this: does ClassBoxes
>>>> require VM-side changes? (Because it changes the method lookup, after
>>>> all, searching packages for methods before working up the inheritance
>>>> tree.) If so, how invasive are they? If not, do we have a ball-park
>>>> estimate of how much work it would be to update ClassBoxes to a more
>>>> recent Squeak/Pharo?
>>>>
>>>> I'm more than happy to do the dogwork. I'd just like to know whether
>>>> I'm signing up for months of work or not.
>>>>
>>>> Thanks!
>>>>
>>>> frank
>>>>
>>>
>>
>>
>





More information about the Pharo-dev mailing list