- Pharo-users - lists.pharo.org

Dictionary whose values are dictionaries

by Stephane Ducasse

Hi I'm looking for an implementation of dictionary whose value is also a dictionary. Stef

May 27, 2017

Re: [Pharo-users] Edit methods protocol by code

by Hilaire

Pharo5, sorry. I used a different code to make it work: org := aClass organization protocolOrganizer. org addProtocolNamed: 'code'. org allMethods do: [:aMethod | org classify: aMethod inProtocolNamed: 'code']. org removeEmptyProtocols. Le 27/05/2017 Ã 03:37, Ben Coman a Ã©crit : > Usual starting question, what version? > cheers -ben > -- Dr. Geo http://drgeo.eu

May 27, 2017

Re: [Pharo-users] Moving Class to a Package programmaticaly

by Hilaire

Thanks Thierry Le 26/05/2017 Ã 19:22, Thierry Goubier a Ã©crit : > > This should work: -- Dr. Geo http://drgeo.eu

May 27, 2017

Re: [Pharo-users] Moving Class to a Package programmaticaly

by Denis Kudriashov

2017-05-27 15:05 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > The problem I foresee is that at a certain point in the future, not > advertised, that semantic will change to not mean 'remove existing tag'. > > If I start using that API, I'll need to add a test in my stuff that will > flag that API semantic change without name change. > That's true. Also you can think that multiple tags are working and implement your code with exta untag logic to ensure singe tag property: aClass untagFrom: #existingTag. aClass tagWith: #newTag

May 27, 2017

Re: [Pharo-users] How to use uFFI with String

by horrido

Yes, I did. I found it difficult to understand. It would be nice to have some clear examples in the documentation, for example, really simple and common situations such as a C function returning an integer in a passed-by-reference argument. Speaking of documentation, in "Pharo by Example 50," I found this statement: > (Recall that you should set halosEnabled in the Preferences browser.) However, nowhere else in the book is there any reference to halosEnabled or Preferences browser. Did you guys forget and leave out a chunk of the book? Stephane Ducasse-3 wrote > Did you read the UFFI chapter? > > https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre… > > https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre… > > > I'm turning it into a booklet but I will not write it because I'm bad in > FFI > Now if you have corrections, suggestions, please do some pull requests > > https://github.com/SquareBracketAssociates/Booklet-uFFI > > Stef > > On Mon, May 22, 2017 at 10:42 PM, horrido < > horrido.hobbies@ > > wrote: > >> There is shockingly very little documentation on how to use uFFI. In >> particular, I have the following situation... >> >> A shared C lib has the following function: >> >> void get_machine(char *machine) { >> uname(&uname_s); >> strcpy(machine, uname_s.machine); >> } >> >> It copies the content of a string value into the buffer passed to it >> (char >> *machine). >> >> I want to call this function from Pharo, thus: >> >> buffer := String new: 64. >> self ffiCall: #( void get_machine(String buffer) ). >> >> The buffer never receives the string value (it just contains the 64 >> initiialized spaces). >> >> Clearly, I'm misunderstanding the proper mechanism for doing this. >> >> [There are other functions in the shared C lib that work fine, such as: >> >> uint get_uptime() { >> sysinfo(&info); >> return info.uptime; >> } >> >> Returning integers or floats is no problem. But passing arguments by >> reference seems to be verboten.] >> >> >> >> -- >> View this message in context: http://forum.world.st/How-to- >> use-uFFI-with-String-tp4947890.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> -- View this message in context: http://forum.world.st/How-to-use-uFFI-with-String-tp4947890p4948427.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 27, 2017

Re: [Pharo-users] Moving Class to a Package programmaticaly

by Thierry Goubier

2017-05-27 14:45 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > > 2017-05-27 14:15 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > >> Will: >> >> #MyPackage asPackage definedClasses do: [:each | each tagWith: #MyPackage] >> >> put the classes in the #MyPackage or in the #MyPackage-MyPackage system >> category? >> > > #tagWith: not touches package of class. It only adds receiver into package > tag. > I not understand the question about system category because I don't know > what it is exactly in current system. > The package and tag names are translated into a 'PackageName-TagName' system category. But: the tag #PackageName has a special meaning in RPackage (for now). It means : what is defined in the package, and not in any other tag. > Now in class definition we have "package: " part. And it will be modified > with new tag-suffix. It will become "package: 'ActualPackageName-TagName'" > Just like it is now in system category then. > > >> >> Will that API stay the same when we will be able to put a class in >> multiple categories (or a method in multiple protocols)? >> > > Yes but #tagWith: will add extra tag into class/method. It will not remove > existing tags. > But in Pharo6 it is only new API. Multiple tags are not supported and > #tagWith: removes existing tag. > > The problem I foresee is that at a certain point in the future, not advertised, that semantic will change to not mean 'remove existing tag'. If I start using that API, I'll need to add a test in my stuff that will flag that API semantic change without name change. Thierry

May 27, 2017

Re: [Pharo-users] Moving Class to a Package programmaticaly

by Denis Kudriashov

2017-05-27 14:15 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > Will: > > #MyPackage asPackage definedClasses do: [:each | each tagWith: #MyPackage] > > put the classes in the #MyPackage or in the #MyPackage-MyPackage system > category? > #tagWith: not touches package of class. It only adds receiver into package tag. I not understand the question about system category because I don't know what it is exactly in current system. Now in class definition we have "package: " part. And it will be modified with new tag-suffix. It will become "package: 'ActualPackageName-TagName'" > > Will that API stay the same when we will be able to put a class in > multiple categories (or a method in multiple protocols)? > Yes but #tagWith: will add extra tag into class/method. It will not remove existing tags. But in Pharo6 it is only new API. Multiple tags are not supported and #tagWith: removes existing tag.

May 27, 2017

Re: [Pharo-users] Moving Class to a Package programmaticaly

by Thierry Goubier

2017-05-27 13:58 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > > 2017-05-26 19:22 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > >> >> This should work: >> >> org := (RPackageOrganizer default packageNamed: 'MyPackage'). >> tag := org addClassTag: #Classes. >> org definedClasses do: [ :aClass | >> aClass category: tag categoryName ]. > > > In Pharo 6 there is new tag API for classes: > > #MyPackage asPackage definedClasses do: [:each | each tagWith: #Classes] > > Will: #MyPackage asPackage definedClasses do: [:each | each tagWith: #MyPackage] put the classes in the #MyPackage or in the #MyPackage-MyPackage system category? Will that API stay the same when we will be able to put a class in multiple categories (or a method in multiple protocols)? Regards, Thierry

May 27, 2017

Re: [Pharo-users] Moving Class to a Package programmaticaly

by Denis Kudriashov

2017-05-26 19:22 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > > This should work: > > org := (RPackageOrganizer default packageNamed: 'MyPackage'). > tag := org addClassTag: #Classes. > org definedClasses do: [ :aClass | > aClass category: tag categoryName ]. In Pharo 6 there is new tag API for classes: #MyPackage asPackage definedClasses do: [:each | each tagWith: #Classes]

May 27, 2017

Re: [Pharo-users] Edit methods protocol by code

by Denis Kudriashov

2017-05-26 11:42 GMT+02:00 Hilaire <hilaire(a)drgeo.eu>: > "Buggy" > org := MyClass organization protocolOrganizer. > org addProtocolNamed: 'code'. > org allProtocols do: [:aProtocol | org moveMethodsFrom: aProtocol name > to: 'code']. > org removeEmptyProtocols. > In Pharo 6 we introduced tags API: (MyClass methodsTaggedWith: #oldProtocol) do: [:each | each tagWith: #code]

May 27, 2017