Re: Package extension. Adding instance variables to classes
Hi Pavel, Thank you for your answer. I actually didnât know about this mechanism. I think it is will do the job :) I have probably to rewrite some parts pf my code to access my variables through privateState. no? Thanks again Abdelghani
On 07 May 2018, at 13:15, pharo-users-request@lists.pharo.org wrote:
Message: 1 Date: Mon, 7 May 2018 13:43:56 +0200 From: Pavel Krivanek <pavel.krivanek@gmail.com <mailto:pavel.krivanek@gmail.com>> To: Any question about pharo is welcome <pharo-users@lists.pharo.org <mailto:pharo-users@lists.pharo.org>> Subject: Re: [Pharo-users] Package extension. Adding instance variables to classes Message-ID: <CAHN2FzeMiBL4Y8asJ0XCjS2AQdxycoN+pbc+Hsd=trMnmuiJqw@mail.gmail.com <mailto:CAHN2FzeMiBL4Y8asJ0XCjS2AQdxycoN+pbc+Hsd=trMnmuiJqw@mail.gmail.com>> Content-Type: text/plain; charset="utf-8"
2018-05-07 12:25 GMT+02:00 Alidra Abdelghani via Pharo-users < pharo-users@lists.pharo.org <mailto:pharo-users@lists.pharo.org>>:
---------- P?eposlan? zpr?va ---------- From: Alidra Abdelghani <alidrandco@yahoo.fr <mailto:alidrandco@yahoo.fr>> To: pharo-users@lists.pharo.org <mailto:pharo-users@lists.pharo.org> Cc: Bcc: Date: Mon, 7 May 2018 11:25:49 +0100 Subject: Package extension. Adding instance variables to classes Hi,
I am working on a package named ClassNamesAnalyzer and I need to add code to third party classes in other packages (for instance the FAMIX-Core package). ?Extending? third party classes with methods is easy; I just need to categorise my methods under the *ClassNamesAnalyzer protocole so that loading my package will load them in the image. However, if I want to add instance variables to theses classes, they are not there when I load the package in a new image.
*So my question is* : is there a way to include instance variables addition to other packages in my package?
Currently not, you should use privateState
*Another question is* : is it good practice to add instance variables to classes in third party packages and is there a way to avoid it (because I am not very confortable with that idea)?
It is not, see FAMIXContainerEntity>>#definedAnnotationTypes how this issue is currently being solved using the privateState.
Cheers, -- Pavel
Thanks in advance, Abdelghani
participants (1)
-
Alidra Abdelghani