On Thu, Apr 30, 2015 at 10:56 PM, stepharo <stepharo@free.fr> wrote:

I'm not sure that it will really help.

Importing from VW to Pharo...

VW package A extended by package B method #b in protocol 'accessing'��

will become

Pharo package A extended by package B method #b in protocol '*B'.

then trying to synchronise from Pharo back to VW will need to somehow reconstruct #b being in protocol 'accessing'

��

The * is handy and we have many other things to improve first.

Yes I understand (but lowering the barrier of entry from VW may bring applications and money to the table (P.S. I know you know that))

cheers -ben

��

Le 30/4/15 16:44, Ben Coman a ��crit :

I saw recently how VisualWorks extensions use normal protocol names
http://ia902605.us.archive.org/25/items/St4u181ClassExtensionsInVisualworks/st4u181.mp4

Now that Pharo has got real package objects with RPackage, how possible is the VW convention?�� It would facilitate porting code.

cheers -ben