Smalltalk › Instantiations

More packaging questions

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

Richard Sargent

More packaging questions

Administrator

There is a rule #ignoreReferenceErrorsInMethodNamed: to ignore undefined references in all methods of the specified name. Is there a similar one for a specific method in a class? e.g. I have a SomeClass class>>#initialize method which uses a *lot* of symbols for state purposes. I would like to have one rule for that method rather than enumerate the 100 or so that the individual rules would otherwise require.

If there isn't yet one, can anyone from Instantiations provide some guidelines on what would be needed to build such an extension?

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/va-smalltalk.
For more options, visit https://groups.google.com/d/optout.

John O'Keefe-3

Re: More packaging questions

Richard -

I'm not clear on what you are asking for. If you have a 100 +/- symbols used for state information, you have to identify them to the packager somehow. The most common way to do this for a particular application is to implement SomeApplication class>>#packagerKnownSymbols to answer an array of the 100 +/- symbols. But perhaps you are looking for a way to compute the content of the array -- something like (SomeClass class>>#initialize) literals will get all the literals in the method. Then you need to reject the literals that represent selectors sent in the method.

Is this what you are looking for or did I miss the point of the question completely?

John

On Tuesday, May 12, 2015 at 2:19:23 PM UTC-4, Richard Sargent wrote:

There is a rule #ignoreReferenceErrorsInMethodNamed: to ignore undefined references in all methods of the specified name. Is there a similar one for a specific method in a class? e.g. I have a SomeClass class>>#initialize method which uses a *lot* of symbols for state purposes. I would like to have one rule for that method rather than enumerate the 100 or so that the individual rules would otherwise require.

If there isn't yet one, can anyone from Instantiations provide some guidelines on what would be needed to build such an extension?

Richard Sargent

Re: More packaging questions

Administrator

On Thursday, May 21, 2015 at 5:36:50 AM UTC-7, John O'Keefe wrote:

I'm not clear on what you are asking for. If you have a 100 +/- symbols used for state information, you have to identify them to the packager somehow. The most common way to do this for a particular application is to implement SomeApplication class>>#packagerKnownSymbols to answer an array of the 100 +/- symbols. But perhaps you are looking for a way to compute the content of the array -- something like (SomeClass class>>#initialize) literals will get all the literals in the method. Then you need to reject the literals that represent selectors sent in the method.

Is this what you are looking for or did I miss the point of the question completely?

Actually, you did a better job of understanding than I did of asking! :-) You answered the question I should have asked. (It's been nearly a decade since I last did any heavy lifting with packaging!)

The reason I asked my original question was the existence of the rule #ignoreReferenceErrorsInMethodNamed: which ignores undefined references in all methods of the specified name. I didn't like the imprecise aspect of that rule, so I was wondering about being able to do the same thing for one specific method. (e.g., the method named #x in the class named #Y, rather than all methods named #x throughout the whole system.) I still have a clinical interest in this topic, but not to the point of making it a feature request.

John

On Tuesday, May 12, 2015 at 2:19:23 PM UTC-4, Richard Sargent wrote:
There is a rule #ignoreReferenceErrorsInMethodNamed: to ignore undefined references in all methods of the specified name. Is there a similar one for a specific method in a class? e.g. I have a SomeClass class>>#initialize method which uses a *lot* of symbols for state purposes. I would like to have one rule for that method rather than enumerate the 100 or so that the individual rules would otherwise require.

If there isn't yet one, can anyone from Instantiations provide some guidelines on what would be needed to build such an extension?