Re: About RPackage
Posted by
Tudor Girba on
Mar 01, 2011; 10:06pm
URL: https://forum.world.st/About-RPackage-tp3330650p3330694.html
This was the main problem in the original implementation because the logic of the organizer also depended on this. So, we took it out and I find this way better :).
Of course, we can create a helper method for compatibility reasons, but no internal logic should depend on this.
Cheers,
Doru
On 1 Mar 2011, at 22:59, Stéphane Ducasse wrote:
> Another point
>
> RPackage>>named: aString
>
> | newPackage |
> newPackage := self new name: aString ;yourself.
> "self organizer registerPackage: newPackage."
> ^ newPackage
>
> does not register the package and this looks suspicion to me.
>
>
> In addition I do not remember the exact logic but the pattern with PackageInfo is that
>
> PackageInfo named: #foo creates the package if it does exist
>
> PackageInfo class>>named: aString
> ^ PackageOrganizer default packageNamed: aString ifAbsent: [(self new packageName: aString) register]
>
> So do you remember because it may be better to have the same creation protocol.
>
> Stef
>
>
>> Hi cyrille/doru and others.
>>
>> I do not understand why
>> RPackage organizer packages contains System?
>>
>> In fact all the categories are mapped to packages and I wonder why.
>> I imagine that this is to avoid to have mostSpecific* logic of packageInfo,
>> but it means that in such a case we should merge categories to get back the package we have right now
>> else we will end up with loading/saving problems.
>>
>>
>> Stef
>
>
--
www.tudorgirba.com
"Be rather willing to give than demanding to get."