July 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Pragmas/Annotations for classes

by StÃ©phane Ducasse

> But i don't understand why i would want to do this? > Let us put it straight and look into roots: > - you want to attach an arbitrary data to a class. > It could be used for anything, like comment, author, stamp, icon etc etc. > Adding just pragmas, for me, looks like too narrow and short-sighted > extension, which not really > helpful nor future-proof. > I'd rather look for something , which would allow me to attach any > meta-data to class, > and corresponding mechanisms to replicate it from/to source code or > binary format(s). > As well, as improve tools support for easy > navigating/inspecting/searching this data. class methods? cheap?

July 9, 2010

[Pharo-project] FFI and global structs (I think)

by Schwab,Wilhelm K

Andreas, I am using FFI to make calls into the Gnu Scientific Library and am having problems that I do not understand. They provide "types" for various algorithms/functions/etc. which appear to be global structs. Suppose I want to use Haar wavelets; then I have interest in what I believe is a struct exported as gls_wavelet_haar. My simple-minded understanding of such things is that "the name is address" and that dlsym()/GetProcAddress() should provide a void pointer to the correct place in memory. My attempts at doing that have ended badly. If I instead export a function of my own (from a library that links to GSL), something like gls_wavelet_type* WaveletHaar() { return gsl_wavelet_haar; } and call it something like waveletTypeHaar < cdecl: GslWaveletType* WaveletHaar()> then all is well. If I use GslWaveletType fromHandle: with an address from dlsym(), ugliness (segment fault) follows. Am I missing something really fundamental, or should #fromHandle: be able to do the job? Bill

July 9, 2010

[Pharo-project] Issues with ObjectiveCPlugin.bundle 1.1.3

by John M McIntosh

Well *cough*, I might have written a couple of dozen tests to check the Objective-C bridge, but obviously if I don't run them, why something broken creeps in. It seems that I managed to make a code change that broke how the unsigned short data is fetched from a objective-c message send. As I was working on the Cog Stack VM for the iPhone today I tripped over the fact that I had somehow managed not to run the test suite. Obviously if I had it would have told me something was busted. I've fixed this and shortly I'll look at building ObjectCPlugin.bundle 1.1.4 and Mac Carbon VM 5.7b2 People who have built their own plugin should fire up VMMaker and rebuild a copy from the latest SqueakSource update -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

July 9, 2010

Re: [Pharo-project] Pragmas/Annotations for classes

by Igor Stasenko

2010/7/9 Guillermo Polito <guillermopolito(a)gmail.com>: > > > On Thu, Jul 8, 2010 at 8:55 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> Guys, i really wonder, how it differs from using a usual smalltalk syntax >> for >> class declaration? >> >> pragmas: '<pragma1> <pragma2>' >> >> can be written as: >> >> pragmas: 'pragma1 pragma2' >> >> without any loss of extensibility/flexibility/whatever. > > Agree, I just put it as an example.Â Indeed I like more your simpler version > :). > >> >> Of course, we can put any sequence of characters into the string >> literal and parse >> them in any way we want to, to extract some extra information. But is >> it worth it? >> But i wonder, why we should invent so over-complicated ways to do simple >> things? >> >> In any way, if we need that class should carry additional information, >> which needs to be formally represented in >> declaration, then i why not just keep using ordinary syntax, by adding >> either additional keywords, or even statements. >> Just look at ProtoObject declaration: >> >> ProtoObject subclass: #ProtoObject >> Â Â Â Â instanceVariableNames: '' >> Â Â Â Â classVariableNames: '' >> Â Â Â Â poolDictionaries: '' >> Â Â Â Â category: 'Kernel-Objects'. >> ProtoObject superclass: nil >> >> if we want to extend this, it is logically to follow the same pattern >> and add any other statements, like: >> >> MyClass foo: bar. > > Do you mean something like... > > ProtoObject subclass: #ProtoObject > Â Â Â Â instanceVariableNames: '' > Â Â Â Â classVariableNames: '' > Â Â Â Â poolDictionaries: '' > Â Â Â Â category: 'Kernel-Objects'. > ProtoObject superclass: nil > ProtoObject pragmas: 'pragma1 pragma2 pragma3' > > ? > That would be nice :D. We decouple the pragmas from the declaration and we > avoid making the combinatory :P. > yes. But i don't understand why i would want to do this? Let us put it straight and look into roots: - you want to attach an arbitrary data to a class. It could be used for anything, like comment, author, stamp, icon etc etc. Adding just pragmas, for me, looks like too narrow and short-sighted extension, which not really helpful nor future-proof. I'd rather look for something , which would allow me to attach any meta-data to class, and corresponding mechanisms to replicate it from/to source code or binary format(s). As well, as improve tools support for easy navigating/inspecting/searching this data. > >> >> Just my 2c. >> >> 2010/7/9 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >> > >> > >> > 2010/7/8 Mariano Martinez Peck <marianopeck(a)gmail.com> >> >> >> >> >> >> 2010/7/8 Guillermo Polito <guillermopolito(a)gmail.com> >> >>> >> >>> Why not add an extension to the #subclass: method family like >> >>> >> >>> Object subclass: #AppRegistry >> >>> Â Â Â instanceVariableNames: '' >> >>> Â Â Â classVariableNames: '' >> >>> Â Â Â poolDictionaries: '' >> >>> Â Â Â pragmas: '<pragma1> <pragma2>' >> >>> Â Â Â category: 'System-Applications' >> >>> >> >> >> >> good idea. But then, you need to have a collection of Pragmas in >> >> Behavior, >> >> ClassDescription or similar.Â Did I understand well? >> >> >> > >> > Would it be easily extensible ? I mean extending the class of another >> > package... >> > >> > Nicolas >> > >> >> >> >> >> >> >> >>> >> >>> ? >> >>> >> >>> On Thu, Jul 8, 2010 at 12:54 PM, Alexandre Bergel >> >>> <alexandre(a)bergel.eu> >> >>> wrote: >> >>>> >> >>>> > May be using a class method? >> >>>> > But yes this would be important. >> >>>> >> >>>> The initialize method of the metaclass maybe. >> >>>> >> >>>> Alexandre >> >>>> >> >>>> > >> >>>> > On Jul 8, 2010, at 3:35 PM, Torsten Bergmann wrote: >> >>>> > >> >>>> >> Hi, >> >>>> >> >> >>>> >> while it is possible to annotate methods using Pragmas, >> >>>> >> what about classes? >> >>>> >> >> >>>> >> Thx >> >>>> >> T. >> >>>> >> -- >> >>>> >> GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! >> >>>> >> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 >> >>>> >> >> >>>> >> _______________________________________________ >> >>>> >> Pharo-project mailing list >> >>>> >> Pharo-project(a)lists.gforge.inria.fr >> >>>> >> >> >>>> >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >>>> > >> >>>> > >> >>>> > _______________________________________________ >> >>>> > Pharo-project mailing list >> >>>> > Pharo-project(a)lists.gforge.inria.fr >> >>>> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >>>> >> >>>> -- >> >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> >>>> Alexandre Bergel Â http://www.bergel.eu >> >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >>>> >> >>>> >> >>>> >> >>>> >> >>>> >> >>>> >> >>>> _______________________________________________ >> >>>> Pharo-project mailing list >> >>>> Pharo-project(a)lists.gforge.inria.fr >> >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >>> >> >>> >> >>> _______________________________________________ >> >>> Pharo-project mailing list >> >>> Pharo-project(a)lists.gforge.inria.fr >> >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> >> >> >> _______________________________________________ >> >> Pharo-project mailing list >> >> Pharo-project(a)lists.gforge.inria.fr >> >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >> > >> > _______________________________________________ >> > Pharo-project mailing list >> > Pharo-project(a)lists.gforge.inria.fr >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

July 9, 2010

Re: [Pharo-project] Pragmas/Annotations for classes

by Guillermo Polito

On Thu, Jul 8, 2010 at 8:55 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > Guys, i really wonder, how it differs from using a usual smalltalk syntax > for > class declaration? > > pragmas: '<pragma1> <pragma2>' > > can be written as: > > pragmas: 'pragma1 pragma2' > without any loss of extensibility/flexibility/whatever. > Agree, I just put it as an example. Indeed I like more your simpler version :). > > Of course, we can put any sequence of characters into the string > literal and parse > them in any way we want to, to extract some extra information. But is > it worth it? > But i wonder, why we should invent so over-complicated ways to do simple > things? > > In any way, if we need that class should carry additional information, > which needs to be formally represented in > declaration, then i why not just keep using ordinary syntax, by adding > either additional keywords, or even statements. > Just look at ProtoObject declaration: > > ProtoObject subclass: #ProtoObject > instanceVariableNames: '' > classVariableNames: '' > poolDictionaries: '' > category: 'Kernel-Objects'. > ProtoObject superclass: nil > > if we want to extend this, it is logically to follow the same pattern > and add any other statements, like: > > MyClass foo: bar. > Do you mean something like... ProtoObject subclass: #ProtoObject instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'Kernel-Objects'. ProtoObject superclass: nil ProtoObject pragmas: 'pragma1 pragma2 pragma3' ? That would be nice :D. We decouple the pragmas from the declaration and we avoid making the combinatory :P. > > Just my 2c. > > 2010/7/9 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: > > > > > > 2010/7/8 Mariano Martinez Peck <marianopeck(a)gmail.com> > >> > >> > >> 2010/7/8 Guillermo Polito <guillermopolito(a)gmail.com> > >>> > >>> Why not add an extension to the #subclass: method family like > >>> > >>> Object subclass: #AppRegistry > >>> instanceVariableNames: '' > >>> classVariableNames: '' > >>> poolDictionaries: '' > >>> pragmas: '<pragma1> <pragma2>' > >>> category: 'System-Applications' > >>> > >> > >> good idea. But then, you need to have a collection of Pragmas in > Behavior, > >> ClassDescription or similar. Did I understand well? > >> > > > > Would it be easily extensible ? I mean extending the class of another > > package... > > > > Nicolas > > > >> > >> > >> > >>> > >>> ? > >>> > >>> On Thu, Jul 8, 2010 at 12:54 PM, Alexandre Bergel <alexandre(a)bergel.eu > > > >>> wrote: > >>>> > >>>> > May be using a class method? > >>>> > But yes this would be important. > >>>> > >>>> The initialize method of the metaclass maybe. > >>>> > >>>> Alexandre > >>>> > >>>> > > >>>> > On Jul 8, 2010, at 3:35 PM, Torsten Bergmann wrote: > >>>> > > >>>> >> Hi, > >>>> >> > >>>> >> while it is possible to annotate methods using Pragmas, > >>>> >> what about classes? > >>>> >> > >>>> >> Thx > >>>> >> T. > >>>> >> -- > >>>> >> GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > >>>> >> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > >>>> >> > >>>> >> _______________________________________________ > >>>> >> Pharo-project mailing list > >>>> >> Pharo-project(a)lists.gforge.inria.fr > >>>> >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>>> > > >>>> > > >>>> > _______________________________________________ > >>>> > Pharo-project mailing list > >>>> > Pharo-project(a)lists.gforge.inria.fr > >>>> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>>> > >>>> -- > >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > >>>> Alexandre Bergel http://www.bergel.eu > >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> Pharo-project mailing list > >>>> Pharo-project(a)lists.gforge.inria.fr > >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>> > >>> > >>> _______________________________________________ > >>> Pharo-project mailing list > >>> Pharo-project(a)lists.gforge.inria.fr > >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 9, 2010

Re: [Pharo-project] Pragmas/Annotations for classes

by Guillermo Polito

2010/7/8 Mariano Martinez Peck <marianopeck(a)gmail.com> > > > 2010/7/8 Guillermo Polito <guillermopolito(a)gmail.com> > > Why not add an extension to the #subclass: method family like >> >> Object subclass: #AppRegistry >> instanceVariableNames: '' >> classVariableNames: '' >> poolDictionaries: '' >> pragmas: '<pragma1> <pragma2>' >> category: 'System-Applications' >> >> > good idea. But then, you need to have a collection of Pragmas in Behavior, > ClassDescription or similar. Did I understand well? > > Here are two mixed up concerns. Where should the class pragmas stored, and where should them be defined. I think it is practical to define them in the class definition... Then they can be stored as: - a collection of pragmas in each class, which make us have a collection per class. - a pragmas string definition in each class, which make us "compile" or "parse" (I don't know how is this working now) the class pragmas when them to a class. - a global dictionary? Puaj. Where would you like to store a class pragma instead? I thought the class or the behaviour was the place to store it... Anyway, where are the method pragmas stored today? In the CompiledMethod? > > > >> ? >> >> >> On Thu, Jul 8, 2010 at 12:54 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: >> >>> > May be using a class method? >>> > But yes this would be important. >>> >>> The initialize method of the metaclass maybe. >>> >>> Alexandre >>> >>> > >>> > On Jul 8, 2010, at 3:35 PM, Torsten Bergmann wrote: >>> > >>> >> Hi, >>> >> >>> >> while it is possible to annotate methods using Pragmas, >>> >> what about classes? >>> >> >>> >> Thx >>> >> T. >>> >> -- >>> >> GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! >>> >> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 >>> >> >>> >> _______________________________________________ >>> >> Pharo-project mailing list >>> >> Pharo-project(a)lists.gforge.inria.fr >>> >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> > >>> > >>> > _______________________________________________ >>> > Pharo-project mailing list >>> > Pharo-project(a)lists.gforge.inria.fr >>> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 8, 2010

Re: [Pharo-project] Pragmas/Annotations for classes

by Igor Stasenko

Guys, i really wonder, how it differs from using a usual smalltalk syntax for class declaration? pragmas: '<pragma1> <pragma2>' can be written as: pragmas: 'pragma1 pragma2' without any loss of extensibility/flexibility/whatever. Of course, we can put any sequence of characters into the string literal and parse them in any way we want to, to extract some extra information. But is it worth it? But i wonder, why we should invent so over-complicated ways to do simple things? In any way, if we need that class should carry additional information, which needs to be formally represented in declaration, then i why not just keep using ordinary syntax, by adding either additional keywords, or even statements. Just look at ProtoObject declaration: ProtoObject subclass: #ProtoObject instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'Kernel-Objects'. ProtoObject superclass: nil if we want to extend this, it is logically to follow the same pattern and add any other statements, like: MyClass foo: bar. Just my 2c. 2010/7/9 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: > > > 2010/7/8 Mariano Martinez Peck <marianopeck(a)gmail.com> >> >> >> 2010/7/8 Guillermo Polito <guillermopolito(a)gmail.com> >>> >>> Why not add an extension to the #subclass: method family like >>> >>> Object subclass: #AppRegistry >>> Â Â Â instanceVariableNames: '' >>> Â Â Â classVariableNames: '' >>> Â Â Â poolDictionaries: '' >>> Â Â Â pragmas: '<pragma1> <pragma2>' >>> Â Â Â category: 'System-Applications' >>> >> >> good idea. But then, you need to have a collection of Pragmas in Behavior, >> ClassDescription or similar.Â Did I understand well? >> > > Would it be easily extensible ? I mean extending the class of another > package... > > Nicolas > >> >> >> >>> >>> ? >>> >>> On Thu, Jul 8, 2010 at 12:54 PM, Alexandre Bergel <alexandre(a)bergel.eu> >>> wrote: >>>> >>>> > May be using a class method? >>>> > But yes this would be important. >>>> >>>> The initialize method of the metaclass maybe. >>>> >>>> Alexandre >>>> >>>> > >>>> > On Jul 8, 2010, at 3:35 PM, Torsten Bergmann wrote: >>>> > >>>> >> Hi, >>>> >> >>>> >> while it is possible to annotate methods using Pragmas, >>>> >> what about classes? >>>> >> >>>> >> Thx >>>> >> T. >>>> >> -- >>>> >> GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! >>>> >> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 >>>> >> >>>> >> _______________________________________________ >>>> >> Pharo-project mailing list >>>> >> Pharo-project(a)lists.gforge.inria.fr >>>> >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> > >>>> > >>>> > _______________________________________________ >>>> > Pharo-project mailing list >>>> > Pharo-project(a)lists.gforge.inria.fr >>>> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel Â http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

July 8, 2010

Re: [Pharo-project] Pragmas/Annotations for classes

by Nicolas Cellier

2010/7/8 Mariano Martinez Peck <marianopeck(a)gmail.com> > > > 2010/7/8 Guillermo Polito <guillermopolito(a)gmail.com> > >> Why not add an extension to the #subclass: method family like >> >> Object subclass: #AppRegistry >> instanceVariableNames: '' >> classVariableNames: '' >> poolDictionaries: '' >> pragmas: '<pragma1> <pragma2>' >> category: 'System-Applications' >> >> > good idea. But then, you need to have a collection of Pragmas in Behavior, > ClassDescription or similar. Did I understand well? > > Would it be easily extensible ? I mean extending the class of another package... Nicolas > > > >> ? >> >> >> On Thu, Jul 8, 2010 at 12:54 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: >> >>> > May be using a class method? >>> > But yes this would be important. >>> >>> The initialize method of the metaclass maybe. >>> >>> Alexandre >>> >>> > >>> > On Jul 8, 2010, at 3:35 PM, Torsten Bergmann wrote: >>> > >>> >> Hi, >>> >> >>> >> while it is possible to annotate methods using Pragmas, >>> >> what about classes? >>> >> >>> >> Thx >>> >> T. >>> >> -- >>> >> GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! >>> >> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 >>> >> >>> >> _______________________________________________ >>> >> Pharo-project mailing list >>> >> Pharo-project(a)lists.gforge.inria.fr >>> >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> > >>> > >>> > _______________________________________________ >>> > Pharo-project mailing list >>> > Pharo-project(a)lists.gforge.inria.fr >>> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 8, 2010

[Pharo-project] Spy?

by Johan Brichau

Hi, I tried to download SPY in a Pharo1.0 image using its Metacello conf, but it told me that I needed MMProbe and ActivityMonitor first. Is SPY working in Pharo 1.0 ? Or not? thx! ---------------------------- Johan Brichau johan.brichau(a)uclouvain.be

July 8, 2010

Re: [Pharo-project] Pragmas/Annotations for classes

by Mariano Martinez Peck

2010/7/8 Guillermo Polito <guillermopolito(a)gmail.com> > Why not add an extension to the #subclass: method family like > > Object subclass: #AppRegistry > instanceVariableNames: '' > classVariableNames: '' > poolDictionaries: '' > pragmas: '<pragma1> <pragma2>' > category: 'System-Applications' > > good idea. But then, you need to have a collection of Pragmas in Behavior, ClassDescription or similar. Did I understand well? > ? > > > On Thu, Jul 8, 2010 at 12:54 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > >> > May be using a class method? >> > But yes this would be important. >> >> The initialize method of the metaclass maybe. >> >> Alexandre >> >> > >> > On Jul 8, 2010, at 3:35 PM, Torsten Bergmann wrote: >> > >> >> Hi, >> >> >> >> while it is possible to annotate methods using Pragmas, >> >> what about classes? >> >> >> >> Thx >> >> T. >> >> -- >> >> GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! >> >> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 >> >> >> >> _______________________________________________ >> >> Pharo-project mailing list >> >> Pharo-project(a)lists.gforge.inria.fr >> >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >> > >> > _______________________________________________ >> > Pharo-project mailing list >> > Pharo-project(a)lists.gforge.inria.fr >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 8, 2010