Smalltalk › Pharo › Pharo Smalltalk Developers

ANSICompatibility package

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

16 messages Options

Jan Vrany

ANSICompatibility package

Hi,

is there actually such a thing like ANSICompatibility package?
(it has been mentioned here lately, but I cannot find it)

Thanks, Jan

Ben Coman

Re: ANSICompatibility package

On Tue, Sep 8, 2015 at 9:21 AM, Jan Vrany <[hidden email]> wrote:
> Hi,
>
> is there actually such a thing like ANSICompatibility package?
> (it has been mentioned here lately, but I cannot find it)
>
> Thanks, Jan
>

I made it up for the purpose of discussion to see what interest it generated.
Should we start one ?
cheers -ben

Jan Vrany

Re: ANSICompatibility package

On Tue, 2015-09-08 at 12:04 +0800, Ben Coman wrote:

> On Tue, Sep 8, 2015 at 9:21 AM, Jan Vrany <[hidden email]>
> wrote:
> > Hi,
> >
> > is there actually such a thing like ANSICompatibility package?
> > (it has been mentioned here lately, but I cannot find it)
> >
> > Thanks, Jan
> >
>
> I made it up for the purpose of discussion to see what interest it
> generated.
> Should we start one ?

Well, let's put it this way: if there would be one, I'd use it and even
contribute adding missing stuff. But I certainly have no time to start
yet another project, having way too much on my plate already.

So `(passes respondsTo: #removeAtIndex:) ifTrue:[...]` would do it.
Quick and dirty, but no time and desire to fight Pharo :-)

Cheers, Jan

> cheers -ben
>

Hannes Hirzel

Re: ANSICompatibility package

Jan,

have a look at

http://wiki.squeak.org/squeak/3172

ca 2800 tests

First thing to do would be to do an quick analysis of the porting effort.

The question is why do not need a ANSI compatibility package.

Grease
http://www.smalltalkhub.com/#!/~Seaside/Grease11
is also an issue to look into for creating portable code.

In the end the incompatible methods in Pharo are often not all that many.

This means that what you mention as 'quick and dirty' is actually
quite a good approach: You test the Smalltalk platform you are using
for the availability of certain methods and act accordingly.

--Hannes

On 9/8/15, Jan Vrany <[hidden email]> wrote:

> On Tue, 2015-09-08 at 12:04 +0800, Ben Coman wrote:
>> On Tue, Sep 8, 2015 at 9:21 AM, Jan Vrany <[hidden email]>
>> wrote:
>> > Hi,
>> >
>> > is there actually such a thing like ANSICompatibility package?
>> > (it has been mentioned here lately, but I cannot find it)
>> >
>> > Thanks, Jan
>> >
>>
>> I made it up for the purpose of discussion to see what interest it
>> generated.
>> Should we start one ?
>
> Well, let's put it this way: if there would be one, I'd use it and even
> contribute adding missing stuff. But I certainly have no time to start
> yet another project, having way too much on my plate already.
>
> So `(passes respondsTo: #removeAtIndex:) ifTrue:[...]` would do it.
> Quick and dirty, but no time and desire to fight Pharo :-)
>
> Cheers, Jan
>
>> cheers -ben
>>
>
>

Jan Vrany

Re: ANSICompatibility package

Hi,

On Tue, 2015-09-08 at 12:04 +0200, H. Hirzel wrote:
> Jan,
>
> have a look at
>
> http://wiki.squeak.org/squeak/3172
>
> ca 2800 tests

Thanks for this, I'll make a note...

>
> First thing to do would be to do an quick analysis of the porting
> effort.
>
> The question is why do not need a ANSI compatibility package.
>
> Grease
> http://www.smalltalkhub.com/#!/~Seaside/Grease11
> is also an issue to look into for creating portable code.
>

Well:

"Grease enhances the ANSI Smalltalk standard. With only a few
exceptions, we assume platforms are fully ANSI-compliant."

So on Pharo, Grease would not help as, IIUC, Pharo is not and
does now want to be, ANSI compliant. This means that
ANSICompatibility is (will be) needed for Grease if Pharo keeps
removing ANSI methods, right?

> In the end the incompatible methods in Pharo are often not all that
> many.
> This means that what you mention as 'quick and dirty' is actually
> quite a good approach: You test the Smalltalk platform you are using
> for the availability of certain methods and act accordingly.

Except it makes the code a lot less comprehensible...
Anyway, problem solved :-)

Jan

>
>
> --Hannes
>
> On 9/8/15, Jan Vrany <[hidden email]> wrote:
> > On Tue, 2015-09-08 at 12:04 +0800, Ben Coman wrote:
> > > On Tue, Sep 8, 2015 at 9:21 AM, Jan Vrany <[hidden email]>
> > > wrote:
> > > > Hi,
> > > >
> > > > is there actually such a thing like ANSICompatibility package?
> > > > (it has been mentioned here lately, but I cannot find it)
> > > >
> > > > Thanks, Jan
> > > >
> > >
> > > I made it up for the purpose of discussion to see what interest
> > > it
> > > generated.
> > > Should we start one ?
> >
> > Well, let's put it this way: if there would be one, I'd use it and
> > even
> > contribute adding missing stuff. But I certainly have no time to
> > start
> > yet another project, having way too much on my plate already.
> >
> > So `(passes respondsTo: #removeAtIndex:) ifTrue:[...]` would do it.
> > Quick and dirty, but no time and desire to fight Pharo :-)
> >
> > Cheers, Jan
> >
> > > cheers -ben
> > >
> >
> >
>

stepharo

Re: ANSICompatibility package

In reply to this post by Ben Coman

We should have a SmalltalkCompatibility (not Ansi per se) package
were we can add some methods to help migration.

Stef

Le 8/9/15 06:04, Ben Coman a écrit :

> On Tue, Sep 8, 2015 at 9:21 AM, Jan Vrany <[hidden email]> wrote:
>> Hi,
>>
>> is there actually such a thing like ANSICompatibility package?
>> (it has been mentioned here lately, but I cannot find it)
>>
>> Thanks, Jan
>>
> I made it up for the purpose of discussion to see what interest it generated.
> Should we start one ?
> cheers -ben
>
>

Torsten Bergmann

Re: ANSICompatibility package

Whoever created http://smalltalkhub.com/#!/~PharoExtras/Compatibility/

I would rename it to SmalltalkCompatibility to ANSICompatibility because
"Compatibility" is a too general term and could mean backward compatibility
of Pharo versions or compatibility to other languages as well.

Also see http://wiki.squeak.org/squeak/2384 and http://map.squeak.org/package/d7011055-4446-4b8e-b6da-e7e32d3389ec
which could be a start.

> Gesendet: Dienstag, 08. September 2015 um 22:53 Uhr
> Von: stepharo <[hidden email]>
> An: "Pharo Development List" <[hidden email]>
> Betreff: Re: [Pharo-dev] ANSICompatibility package
>
> We should have a SmalltalkCompatibility (not Ansi per se) package
> were we can add some methods to help migration.
>
> Stef
>
>
> Le 8/9/15 06:04, Ben Coman a écrit :
> > On Tue, Sep 8, 2015 at 9:21 AM, Jan Vrany <[hidden email]> wrote:
> >> Hi,
> >>
> >> is there actually such a thing like ANSICompatibility package?
> >> (it has been mentioned here lately, but I cannot find it)
> >>
> >> Thanks, Jan
> >>
> > I made it up for the purpose of discussion to see what interest it generated.
> > Should we start one ?
> > cheers -ben
> >
> >
>
>
>

Jan Vrany

Re: ANSICompatibility package

On Wed, 2015-09-09 at 10:31 +0200, Torsten Bergmann wrote:
> Whoever created
> http://smalltalkhub.com/#!/~PharoExtras/Compatibility/
>
> I would rename it to SmalltalkCompatibility to ANSICompatibility
> because
> "Compatibility" is a too general term and could mean backward
> compatibility
> of Pharo versions or compatibility to other languages as well.

+1 to ANSICompatibility

>
> Also see http://wiki.squeak.org/squeak/2384 and
> http://map.squeak.org/package/d7011055-4446-4b8e-b6da-e7e32d3389ec
> which could be a start.
>
>
> > Gesendet: Dienstag, 08. September 2015 um 22:53 Uhr
> > Von: stepharo <[hidden email]>
> > An: "Pharo Development List" <[hidden email]>
> > Betreff: Re: [Pharo-dev] ANSICompatibility package
> >
> > We should have a SmalltalkCompatibility (not Ansi per se) package
> > were we can add some methods to help migration.
> >
> > Stef
> >
> >
> > Le 8/9/15 06:04, Ben Coman a écrit :
> > > On Tue, Sep 8, 2015 at 9:21 AM, Jan Vrany <[hidden email]>
> > > wrote:
> > > > Hi,
> > > >
> > > > is there actually such a thing like ANSICompatibility package?
> > > > (it has been mentioned here lately, but I cannot find it)
> > > >
> > > > Thanks, Jan
> > > >
> > > I made it up for the purpose of discussion to see what interest
> > > it generated.
> > > Should we start one ?
> > > cheers -ben
> > >
> > >
> >
> >
> >
>
>

Ben Coman

Re: ANSICompatibility package

In reply to this post by Torsten Bergmann

On Wed, Sep 9, 2015 at 4:31 PM, Torsten Bergmann <[hidden email]> wrote:
> Whoever created http://smalltalkhub.com/#!/~PharoExtras/Compatibility/
>
> I would rename it to SmalltalkCompatibility to ANSICompatibility because
> "Compatibility" is a too general term and could mean backward compatibility
> of Pharo versions or compatibility to other languages as well.

That was me :) I was thinking more broadly that over time the
"repository" might hold different packages Compatibility-ANSI,
Compatibility-VW, Compatibility-Dolphin. But maybe that is
overreaching and its better to be more focussed. Let me know what you
think on this and restate what you think the repository name should
be.

> Also see http://wiki.squeak.org/squeak/2384 and http://map.squeak.org/package/d7011055-4446-4b8e-b6da-e7e32d3389ec
> which could be a start.

I saw those, but they interact with existing classes, so I thought it
easier to kickstart by loading in the tests first, which are all new
classes. I only created the repository since the tests were *hard* to
find eventually at
http://www.spacmunke.org/svn/jst/trunk/src/test/ansi/ansi-compatibility/
So I thought it would be good make them more accessible as a Monticello Package.

cheers -ben

P.S. I don't quite follow "to SmalltalkCompatibility to ANSICompatibility"
do you mean "to SmalltalkCompatibility or ANSICompatibility" ?

>
>> Gesendet: Dienstag, 08. September 2015 um 22:53 Uhr
>> Von: stepharo <[hidden email]>
>> An: "Pharo Development List" <[hidden email]>
>> Betreff: Re: [Pharo-dev] ANSICompatibility package
>>
>> We should have a SmalltalkCompatibility (not Ansi per se) package
>> were we can add some methods to help migration.
>>
>> Stef
>>
>>
>> Le 8/9/15 06:04, Ben Coman a écrit :
>> > On Tue, Sep 8, 2015 at 9:21 AM, Jan Vrany <[hidden email]> wrote:
>> >> Hi,
>> >>
>> >> is there actually such a thing like ANSICompatibility package?
>> >> (it has been mentioned here lately, but I cannot find it)
>> >>
>> >> Thanks, Jan
>> >>
>> > I made it up for the purpose of discussion to see what interest it generated.
>> > Should we start one ?
>> > cheers -ben
>> >
>> >
>>
>>
>>
>

Jan Vrany

Re: ANSICompatibility package

> > I would rename it to SmalltalkCompatibility to ANSICompatibility
> > because
> > "Compatibility" is a too general term and could mean backward
> > compatibility
> > of Pharo versions or compatibility to other languages as well.
>
> That was me :) I was thinking more broadly that over time the
> "repository" might hold different packages Compatibility-ANSI,
> Compatibility-VW, Compatibility-Dolphin. But maybe that is
> overreaching and its better to be more focussed. Let me know what you
> think on this and restate what you think the repository name should
> be.

Ben, could you please give me a commit access? I intend to
move Compatibility-SmalltalkX and Compatibility-ANSI (which
I created and "maintain" for my own need). Maybe some others
may find them useful or maybe even contribute.

Cheers, Jan

>
> > Also see http://wiki.squeak.org/squeak/2384 and
> > http://map.squeak.org/package/d7011055-4446-4b8e-b6da-e7e32d3389ec
> > which could be a start.
>
> I saw those, but they interact with existing classes, so I thought it
> easier to kickstart by loading in the tests first, which are all new
> classes. I only created the repository since the tests were *hard*
> to
> find eventually at
> http://www.spacmunke.org/svn/jst/trunk/src/test/ansi/ansi-compatibili
> ty/
> So I thought it would be good make them more accessible as a
> Monticello Package.
>
> cheers -ben
>
> P.S. I don't quite follow "to SmalltalkCompatibility to
> ANSICompatibility"
> do you mean "to SmalltalkCompatibility or ANSICompatibility" ?
>
> >
> > > Gesendet: Dienstag, 08. September 2015 um 22:53 Uhr
> > > Von: stepharo <[hidden email]>
> > > An: "Pharo Development List" <[hidden email]>
> > > Betreff: Re: [Pharo-dev] ANSICompatibility package
> > >
> > > We should have a SmalltalkCompatibility (not Ansi per se) package
> > > were we can add some methods to help migration.
> > >
> > > Stef
> > >
> > >
> > > Le 8/9/15 06:04, Ben Coman a écrit :
> > > > On Tue, Sep 8, 2015 at 9:21 AM, Jan Vrany <
> > > > [hidden email]> wrote:
> > > > > Hi,
> > > > >
> > > > > is there actually such a thing like ANSICompatibility
> > > > > package?
> > > > > (it has been mentioned here lately, but I cannot find it)
> > > > >
> > > > > Thanks, Jan
> > > > >
> > > > I made it up for the purpose of discussion to see what interest
> > > > it generated.
> > > > Should we start one ?
> > > > cheers -ben
> > > >
> > > >
> > >
> > >
> > >
> >
>
>

Ben Coman

Re: ANSICompatibility package

Jan, Thanks for your contribution. Actually I hadn't uploaded anything
yet since I was waiting on more votes on renaming, but to push ahead I
settled on SmalltalkCompatibility [1], since I think the repo can
serve a wider purpose than just ANSI.

I added you to the PharoExtras team. Hopefully that works.

[1] http://smalltalkhub.com/#!/~PharoExtras/SmalltalkCompatibility

cheers -ben

On Fri, Sep 18, 2015 at 7:10 PM, Jan Vrany <[hidden email]> wrote:

>
>> > I would rename it to SmalltalkCompatibility to ANSICompatibility
>> > because "Compatibility" is a too general term and could mean
>> > backward compatibility
>> > of Pharo versions or compatibility to other languages as well.
>>
>> That was me :) I was thinking more broadly that over time the
>> "repository" might hold different packages Compatibility-ANSI,
>> Compatibility-VW, Compatibility-Dolphin. But maybe that is
>> overreaching and its better to be more focussed. Let me know what you
>> think on this and restate what you think the repository name should
>> be.
>
> Ben, could you please give me a commit access? I intend to
> move Compatibility-SmalltalkX and Compatibility-ANSI (which
> I created and "maintain" for my own need). Maybe some others
> may find them useful or maybe even contribute.
>
> Cheers, Jan
>
>>
>> > Also see http://wiki.squeak.org/squeak/2384 and
>> > http://map.squeak.org/package/d7011055-4446-4b8e-b6da-e7e32d3389ec
>> > which could be a start.
>>
>> I saw those, but they interact with existing classes, so I thought it
>> easier to kickstart by loading in the tests first, which are all new
>> classes. I only created the repository since the tests were *hard*
>> to
>> find eventually at
>> http://www.spacmunke.org/svn/jst/trunk/src/test/ansi/ansi-compatibili
>> ty/
>> So I thought it would be good make them more accessible as a
>> Monticello Package.
>>
>> cheers -ben
>>
>> P.S. I don't quite follow "to SmalltalkCompatibility to
>> ANSICompatibility"
>> do you mean "to SmalltalkCompatibility or ANSICompatibility" ?
>>
>> >
>> > > Gesendet: Dienstag, 08. September 2015 um 22:53 Uhr
>> > > Von: stepharo <[hidden email]>
>> > > An: "Pharo Development List" <[hidden email]>
>> > > Betreff: Re: [Pharo-dev] ANSICompatibility package
>> > >
>> > > We should have a SmalltalkCompatibility (not Ansi per se) package
>> > > were we can add some methods to help migration.
>> > >
>> > > Stef
>> > >
>> > >
>> > > Le 8/9/15 06:04, Ben Coman a écrit :
>> > > > On Tue, Sep 8, 2015 at 9:21 AM, Jan Vrany <
>> > > > [hidden email]> wrote:
>> > > > > Hi,
>> > > > >
>> > > > > is there actually such a thing like ANSICompatibility
>> > > > > package?
>> > > > > (it has been mentioned here lately, but I cannot find it)
>> > > > >
>> > > > > Thanks, Jan
>> > > > >
>> > > > I made it up for the purpose of discussion to see what interest
>> > > > it generated.
>> > > > Should we start one ?
>> > > > cheers -ben
>> > > >
>> > > >
>> > >
>> > >
>> > >
>> >
>>
>>
>

Jan Vrany

Re: ANSICompatibility package

Thanks, Ben. Stuff copied.

Cheers, Jan

On Fri, 2015-09-18 at 21:54 +0800, Ben Coman wrote:

> Jan, Thanks for your contribution. Actually I hadn't uploaded
> anything
> yet since I was waiting on more votes on renaming, but to push ahead
> I
> settled on SmalltalkCompatibility [1], since I think the repo can
> serve a wider purpose than just ANSI.
>
> I added you to the PharoExtras team. Hopefully that works.
>
> [1] http://smalltalkhub.com/#!/~PharoExtras/SmalltalkCompatibility
>
> cheers -ben
>
> On Fri, Sep 18, 2015 at 7:10 PM, Jan Vrany <[hidden email]>
> wrote:
> >
> > > > I would rename it to SmalltalkCompatibility to
> > > > ANSICompatibility
> > > > because "Compatibility" is a too general term and could mean
> > > > backward compatibility
> > > > of Pharo versions or compatibility to other languages as well.
> > >
> > > That was me :) I was thinking more broadly that over time the
> > > "repository" might hold different packages Compatibility-ANSI,
> > > Compatibility-VW, Compatibility-Dolphin. But maybe that is
> > > overreaching and its better to be more focussed. Let me know what
> > > you
> > > think on this and restate what you think the repository name
> > > should
> > > be.
> >
> > Ben, could you please give me a commit access? I intend to
> > move Compatibility-SmalltalkX and Compatibility-ANSI (which
> > I created and "maintain" for my own need). Maybe some others
> > may find them useful or maybe even contribute.
> >
> > Cheers, Jan
> >
> > >
> > > > Also see http://wiki.squeak.org/squeak/2384 and
> > > > http://map.squeak.org/package/d7011055-4446-4b8e-b6da-e7e32d338
> > > > 9ec
> > > > which could be a start.
> > >
> > > I saw those, but they interact with existing classes, so I
> > > thought it
> > > easier to kickstart by loading in the tests first, which are all
> > > new
> > > classes. I only created the repository since the tests were
> > > *hard*
> > > to
> > > find eventually at
> > > http://www.spacmunke.org/svn/jst/trunk/src/test/ansi/ansi-compati
> > > bili
> > > ty/
> > > So I thought it would be good make them more accessible as a
> > > Monticello Package.
> > >
> > > cheers -ben
> > >
> > > P.S. I don't quite follow "to SmalltalkCompatibility to
> > > ANSICompatibility"
> > > do you mean "to SmalltalkCompatibility or ANSICompatibility" ?
> > >
> > > >
> > > > > Gesendet: Dienstag, 08. September 2015 um 22:53 Uhr
> > > > > Von: stepharo <[hidden email]>
> > > > > An: "Pharo Development List" <[hidden email]>
> > > > > Betreff: Re: [Pharo-dev] ANSICompatibility package
> > > > >
> > > > > We should have a SmalltalkCompatibility (not Ansi per se)
> > > > > package
> > > > > were we can add some methods to help migration.
> > > > >
> > > > > Stef
> > > > >
> > > > >
> > > > > Le 8/9/15 06:04, Ben Coman a écrit :
> > > > > > On Tue, Sep 8, 2015 at 9:21 AM, Jan Vrany <
> > > > > > [hidden email]> wrote:
> > > > > > > Hi,
> > > > > > >
> > > > > > > is there actually such a thing like ANSICompatibility
> > > > > > > package?
> > > > > > > (it has been mentioned here lately, but I cannot find it)
> > > > > > >
> > > > > > > Thanks, Jan
> > > > > > >
> > > > > > I made it up for the purpose of discussion to see what
> > > > > > interest
> > > > > > it generated.
> > > > > > Should we start one ?
> > > > > > cheers -ben
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> >
>
>

Lorenzo

R: ANSICompatibility package

In reply to this post by Ben Coman

Hi Ben,

I am available if you want to include VisualSmalltalk into ANSICompatibility package.
I have both full documentation and lot of applications.

Lorenzo

-----Messaggio originale-----
Da: Pharo-dev [mailto:[hidden email]] Per conto di Ben Coman
Inviato: venerdì 18 settembre 2015 15:54
A: Pharo Development List
Oggetto: Re: [Pharo-dev] ANSICompatibility package

Jan, Thanks for your contribution. Actually I hadn't uploaded anything yet since I was waiting on more votes on renaming, but to push ahead I settled on SmalltalkCompatibility [1], since I think the repo can serve a wider purpose than just ANSI.

I added you to the PharoExtras team. Hopefully that works.

[1] http://smalltalkhub.com/#!/~PharoExtras/SmalltalkCompatibility

cheers -ben

On Fri, Sep 18, 2015 at 7:10 PM, Jan Vrany <[hidden email]> wrote:

>
>> > I would rename it to SmalltalkCompatibility to ANSICompatibility
>> > because "Compatibility" is a too general term and could mean
>> > backward compatibility of Pharo versions or compatibility to other
>> > languages as well.
>>
>> That was me :) I was thinking more broadly that over time the
>> "repository" might hold different packages Compatibility-ANSI,
>> Compatibility-VW, Compatibility-Dolphin. But maybe that is
>> overreaching and its better to be more focussed. Let me know what you
>> think on this and restate what you think the repository name should
>> be.
>
> Ben, could you please give me a commit access? I intend to move
> Compatibility-SmalltalkX and Compatibility-ANSI (which I created and
> "maintain" for my own need). Maybe some others may find them useful or
> maybe even contribute.
>
> Cheers, Jan
>
>>
>> > Also see http://wiki.squeak.org/squeak/2384 and
>> > http://map.squeak.org/package/d7011055-4446-4b8e-b6da-e7e32d3389ec
>> > which could be a start.
>>
>> I saw those, but they interact with existing classes, so I thought it
>> easier to kickstart by loading in the tests first, which are all new
>> classes. I only created the repository since the tests were *hard*
>> to find eventually at
>> http://www.spacmunke.org/svn/jst/trunk/src/test/ansi/ansi-compatibili
>> ty/
>> So I thought it would be good make them more accessible as a
>> Monticello Package.
>>
>> cheers -ben
>>
>> P.S. I don't quite follow "to SmalltalkCompatibility to
>> ANSICompatibility"
>> do you mean "to SmalltalkCompatibility or ANSICompatibility" ?
>>
>> >
>> > > Gesendet: Dienstag, 08. September 2015 um 22:53 Uhr
>> > > Von: stepharo <[hidden email]>
>> > > An: "Pharo Development List" <[hidden email]>
>> > > Betreff: Re: [Pharo-dev] ANSICompatibility package
>> > >
>> > > We should have a SmalltalkCompatibility (not Ansi per se) package
>> > > were we can add some methods to help migration.
>> > >
>> > > Stef
>> > >
>> > >
>> > > Le 8/9/15 06:04, Ben Coman a écrit :
>> > > > On Tue, Sep 8, 2015 at 9:21 AM, Jan Vrany <
>> > > > [hidden email]> wrote:
>> > > > > Hi,
>> > > > >
>> > > > > is there actually such a thing like ANSICompatibility
>> > > > > package?
>> > > > > (it has been mentioned here lately, but I cannot find it)
>> > > > >
>> > > > > Thanks, Jan
>> > > > >
>> > > > I made it up for the purpose of discussion to see what interest
>> > > > it generated.
>> > > > Should we start one ?
>> > > > cheers -ben
>> > > >
>> > > >
>> > >
>> > >
>> > >
>> >
>>
>>
>

Ben Coman

Re: R: ANSICompatibility package

Thanks Lorenzo, but I'm not clear what the offer is...
* making VisualSmalltalk compatible with ANSI ?
* making Pharo compatible with VisualSmalltalk ?
cheers -ben

On Fri, Sep 18, 2015 at 10:09 PM, Lorenzo Schiavina <[hidden email]> wrote:

> Hi Ben,
>
> I am available if you want to include VisualSmalltalk into ANSICompatibility package.
> I have both full documentation and lot of applications.
>
> Lorenzo
>
> -----Messaggio originale-----
> Da: Pharo-dev [mailto:[hidden email]] Per conto di Ben Coman
> Inviato: venerdì 18 settembre 2015 15:54
> A: Pharo Development List
> Oggetto: Re: [Pharo-dev] ANSICompatibility package
>
> Jan, Thanks for your contribution. Actually I hadn't uploaded anything yet since I was waiting on more votes on renaming, but to push ahead I settled on SmalltalkCompatibility [1], since I think the repo can serve a wider purpose than just ANSI.
>
> I added you to the PharoExtras team. Hopefully that works.
>
> [1] http://smalltalkhub.com/#!/~PharoExtras/SmalltalkCompatibility
>
> cheers -ben
>
> On Fri, Sep 18, 2015 at 7:10 PM, Jan Vrany <[hidden email]> wrote:
>>
>>> > I would rename it to SmalltalkCompatibility to ANSICompatibility
>>> > because "Compatibility" is a too general term and could mean
>>> > backward compatibility of Pharo versions or compatibility to other
>>> > languages as well.
>>>
>>> That was me :) I was thinking more broadly that over time the
>>> "repository" might hold different packages Compatibility-ANSI,
>>> Compatibility-VW, Compatibility-Dolphin. But maybe that is
>>> overreaching and its better to be more focussed. Let me know what you
>>> think on this and restate what you think the repository name should
>>> be.
>>
>> Ben, could you please give me a commit access? I intend to move
>> Compatibility-SmalltalkX and Compatibility-ANSI (which I created and
>> "maintain" for my own need). Maybe some others may find them useful or
>> maybe even contribute.
>>
>> Cheers, Jan
>>
>>>
>>> > Also see http://wiki.squeak.org/squeak/2384 and
>>> > http://map.squeak.org/package/d7011055-4446-4b8e-b6da-e7e32d3389ec
>>> > which could be a start.
>>>
>>> I saw those, but they interact with existing classes, so I thought it
>>> easier to kickstart by loading in the tests first, which are all new
>>> classes. I only created the repository since the tests were *hard*
>>> to find eventually at
>>> http://www.spacmunke.org/svn/jst/trunk/src/test/ansi/ansi-compatibili
>>> ty/
>>> So I thought it would be good make them more accessible as a
>>> Monticello Package.
>>>
>>> cheers -ben
>>>
>>> P.S. I don't quite follow "to SmalltalkCompatibility to
>>> ANSICompatibility"
>>> do you mean "to SmalltalkCompatibility or ANSICompatibility" ?
>>>
>>> >
>>> > > Gesendet: Dienstag, 08. September 2015 um 22:53 Uhr
>>> > > Von: stepharo <[hidden email]>
>>> > > An: "Pharo Development List" <[hidden email]>
>>> > > Betreff: Re: [Pharo-dev] ANSICompatibility package
>>> > >
>>> > > We should have a SmalltalkCompatibility (not Ansi per se) package
>>> > > were we can add some methods to help migration.
>>> > >
>>> > > Stef
>>> > >
>>> > >
>>> > > Le 8/9/15 06:04, Ben Coman a écrit :
>>> > > > On Tue, Sep 8, 2015 at 9:21 AM, Jan Vrany <
>>> > > > [hidden email]> wrote:
>>> > > > > Hi,
>>> > > > >
>>> > > > > is there actually such a thing like ANSICompatibility
>>> > > > > package?
>>> > > > > (it has been mentioned here lately, but I cannot find it)
>>> > > > >
>>> > > > > Thanks, Jan
>>> > > > >
>>> > > > I made it up for the purpose of discussion to see what interest
>>> > > > it generated.
>>> > > > Should we start one ?
>>> > > > cheers -ben
>>> > > >
>>> > > >
>>> > >
>>> > >
>>> > >
>>> >
>>>
>>>
>>
>
>

Ben Coman

Re: ANSICompatibility package

In reply to this post by Jan Vrany

Thanks for your contribution Jan. It is interesting how in
"CompatibilitySmalltalkX class>>initialize" you deal with missing
classes by inserting what are essentially alias into the Smalltalk
dictionary. So, I'm happy I learnt something new today.

Just curious though why both the class-side and instance-side
#initialize methods set the same alias, but different ways.

Also curious why "ClassDescription>>isClass" is blank. It would seem
to need a boolean return value.

cheers -ben

On Fri, Sep 18, 2015 at 10:05 PM, Jan Vrany <[hidden email]> wrote:

> Thanks, Ben. Stuff copied.
>
> Cheers, Jan
>
>
> On Fri, 2015-09-18 at 21:54 +0800, Ben Coman wrote:
>> Jan, Thanks for your contribution. Actually I hadn't uploaded
>> anything
>> yet since I was waiting on more votes on renaming, but to push ahead
>> I
>> settled on SmalltalkCompatibility [1], since I think the repo can
>> serve a wider purpose than just ANSI.
>>
>> I added you to the PharoExtras team. Hopefully that works.
>>
>> [1] http://smalltalkhub.com/#!/~PharoExtras/SmalltalkCompatibility
>>
>> cheers -ben
>>
>> On Fri, Sep 18, 2015 at 7:10 PM, Jan Vrany <[hidden email]>
>> wrote:
>> >
>> > > > I would rename it to SmalltalkCompatibility to
>> > > > ANSICompatibility
>> > > > because "Compatibility" is a too general term and could mean
>> > > > backward compatibility
>> > > > of Pharo versions or compatibility to other languages as well.
>> > >
>> > > That was me :) I was thinking more broadly that over time the
>> > > "repository" might hold different packages Compatibility-ANSI,
>> > > Compatibility-VW, Compatibility-Dolphin. But maybe that is
>> > > overreaching and its better to be more focussed. Let me know what
>> > > you
>> > > think on this and restate what you think the repository name
>> > > should
>> > > be.
>> >
>> > Ben, could you please give me a commit access? I intend to
>> > move Compatibility-SmalltalkX and Compatibility-ANSI (which
>> > I created and "maintain" for my own need). Maybe some others
>> > may find them useful or maybe even contribute.
>> >
>> > Cheers, Jan
>> >
>> > >
>> > > > Also see http://wiki.squeak.org/squeak/2384 and
>> > > > http://map.squeak.org/package/d7011055-4446-4b8e-b6da-e7e32d338
>> > > > 9ec
>> > > > which could be a start.
>> > >
>> > > I saw those, but they interact with existing classes, so I
>> > > thought it
>> > > easier to kickstart by loading in the tests first, which are all
>> > > new
>> > > classes. I only created the repository since the tests were
>> > > *hard*
>> > > to
>> > > find eventually at
>> > > http://www.spacmunke.org/svn/jst/trunk/src/test/ansi/ansi-compati
>> > > bili
>> > > ty/
>> > > So I thought it would be good make them more accessible as a
>> > > Monticello Package.
>> > >
>> > > cheers -ben
>> > >
>> > > P.S. I don't quite follow "to SmalltalkCompatibility to
>> > > ANSICompatibility"
>> > > do you mean "to SmalltalkCompatibility or ANSICompatibility" ?
>> > >
>> > > >
>> > > > > Gesendet: Dienstag, 08. September 2015 um 22:53 Uhr
>> > > > > Von: stepharo <[hidden email]>
>> > > > > An: "Pharo Development List" <[hidden email]>
>> > > > > Betreff: Re: [Pharo-dev] ANSICompatibility package
>> > > > >
>> > > > > We should have a SmalltalkCompatibility (not Ansi per se)
>> > > > > package
>> > > > > were we can add some methods to help migration.
>> > > > >
>> > > > > Stef
>> > > > >
>> > > > >
>> > > > > Le 8/9/15 06:04, Ben Coman a écrit :
>> > > > > > On Tue, Sep 8, 2015 at 9:21 AM, Jan Vrany <
>> > > > > > [hidden email]> wrote:
>> > > > > > > Hi,
>> > > > > > >
>> > > > > > > is there actually such a thing like ANSICompatibility
>> > > > > > > package?
>> > > > > > > (it has been mentioned here lately, but I cannot find it)
>> > > > > > >
>> > > > > > > Thanks, Jan
>> > > > > > >
>> > > > > > I made it up for the purpose of discussion to see what
>> > > > > > interest
>> > > > > > it generated.
>> > > > > > Should we start one ?
>> > > > > > cheers -ben
>> > > > > >
>> > > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > >
>> > >
>> > >
>> >
>>
>>
>

Jan Vrany

Re: ANSICompatibility package

On Fri, 2015-09-18 at 23:04 +0800, Ben Coman wrote:
> Thanks for your contribution Jan. It is interesting how in
> "CompatibilitySmalltalkX class>>initialize" you deal with missing
> classes by inserting what are essentially alias into the Smalltalk
> dictionary. So, I'm happy I learnt something new today.
>
> Just curious though why both the class-side and instance-side
> #initialize methods set the same alias, but different ways.

Well, this is (was) a bug, I by mistake defined the method on instance
side (where it makes no sense). The Nautilus UI is rather stupid in
that respect, not making clear whether what you see is class side
or instance side...

>
> Also curious why "ClassDescription>>isClass" is blank. It would seem
> to need a boolean return value.

Accident, should be removed.

Both issues fixed in Compatibility-SmalltalkX-JanVrany.11
Thanks for spotting!

Jan

>
> cheers -ben
>
> On Fri, Sep 18, 2015 at 10:05 PM, Jan Vrany <[hidden email]>
> wrote:
> > Thanks, Ben. Stuff copied.
> >
> > Cheers, Jan
> >
> >
> > On Fri, 2015-09-18 at 21:54 +0800, Ben Coman wrote:
> > > Jan, Thanks for your contribution. Actually I hadn't uploaded
> > > anything
> > > yet since I was waiting on more votes on renaming, but to push
> > > ahead
> > > I
> > > settled on SmalltalkCompatibility [1], since I think the repo can
> > > serve a wider purpose than just ANSI.
> > >
> > > I added you to the PharoExtras team. Hopefully that works.
> > >
> > > [1]
> > > http://smalltalkhub.com/#!/~PharoExtras/SmalltalkCompatibility
> > >
> > > cheers -ben
> > >
> > > On Fri, Sep 18, 2015 at 7:10 PM, Jan Vrany <[hidden email]
> > > >
> > > wrote:
> > > >
> > > > > > I would rename it to SmalltalkCompatibility to
> > > > > > ANSICompatibility
> > > > > > because "Compatibility" is a too general term and could
> > > > > > mean
> > > > > > backward compatibility
> > > > > > of Pharo versions or compatibility to other languages as
> > > > > > well.
> > > > >
> > > > > That was me :) I was thinking more broadly that over time
> > > > > the
> > > > > "repository" might hold different packages Compatibility
> > > > > -ANSI,
> > > > > Compatibility-VW, Compatibility-Dolphin. But maybe that is
> > > > > overreaching and its better to be more focussed. Let me know
> > > > > what
> > > > > you
> > > > > think on this and restate what you think the repository name
> > > > > should
> > > > > be.
> > > >
> > > > Ben, could you please give me a commit access? I intend to
> > > > move Compatibility-SmalltalkX and Compatibility-ANSI (which
> > > > I created and "maintain" for my own need). Maybe some others
> > > > may find them useful or maybe even contribute.
> > > >
> > > > Cheers, Jan
> > > >
> > > > >
> > > > > > Also see http://wiki.squeak.org/squeak/2384 and
> > > > > > http://map.squeak.org/package/d7011055-4446-4b8e-b6da-e7e32
> > > > > > d338
> > > > > > 9ec
> > > > > > which could be a start.
> > > > >
> > > > > I saw those, but they interact with existing classes, so I
> > > > > thought it
> > > > > easier to kickstart by loading in the tests first, which are
> > > > > all
> > > > > new
> > > > > classes. I only created the repository since the tests were
> > > > > *hard*
> > > > > to
> > > > > find eventually at
> > > > > http://www.spacmunke.org/svn/jst/trunk/src/test/ansi/ansi-com
> > > > > pati
> > > > > bili
> > > > > ty/
> > > > > So I thought it would be good make them more accessible as a
> > > > > Monticello Package.
> > > > >
> > > > > cheers -ben
> > > > >
> > > > > P.S. I don't quite follow "to SmalltalkCompatibility to
> > > > > ANSICompatibility"
> > > > > do you mean "to SmalltalkCompatibility or ANSICompatibility"
> > > > > ?
> > > > >
> > > > > >
> > > > > > > Gesendet: Dienstag, 08. September 2015 um 22:53 Uhr
> > > > > > > Von: stepharo <[hidden email]>
> > > > > > > An: "Pharo Development List" <[hidden email]>
> > > > > > > Betreff: Re: [Pharo-dev] ANSICompatibility package
> > > > > > >
> > > > > > > We should have a SmalltalkCompatibility (not Ansi per se)
> > > > > > > package
> > > > > > > were we can add some methods to help migration.
> > > > > > >
> > > > > > > Stef
> > > > > > >
> > > > > > >
> > > > > > > Le 8/9/15 06:04, Ben Coman a écrit :
> > > > > > > > On Tue, Sep 8, 2015 at 9:21 AM, Jan Vrany <
> > > > > > > > [hidden email]> wrote:
> > > > > > > > > Hi,
> > > > > > > > >
> > > > > > > > > is there actually such a thing like ANSICompatibility
> > > > > > > > > package?
> > > > > > > > > (it has been mentioned here lately, but I cannot find
> > > > > > > > > it)
> > > > > > > > >
> > > > > > > > > Thanks, Jan
> > > > > > > > >
> > > > > > > > I made it up for the purpose of discussion to see what
> > > > > > > > interest
> > > > > > > > it generated.
> > > > > > > > Should we start one ?
> > > > > > > > cheers -ben
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> >
>
>