Re: [Pharo-project] Question about RPackage (bug?)
You're right! But notice that the RPackage logic of one to one mapping with categories, only breaks when it only provides extension methods as in the case of 'AST-Core' and 'RPackage'. | p | p := RPackageOrganizer default packageNamed: 'AST-Core'. ( p extensionMethods size = 2 ) & ( p definedClasses size = 0 ) Only then, maybe this is a bug? On Thu, Aug 9, 2012 at 1:52 PM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Thu, Aug 9, 2012 at 1:25 PM, Fernando Olivero <fernando.olivero@usi.ch<mailto:fernando.olivero@usi.ch>> wrote: Hi Mariano,
I've been using RPackage so i stumbled on the same "problem". RPackage maps System Categories (one to one), thus your problem happens because there's no category named 'RPackage'.
But for the rest it works. For example:
(RPackageOrganizer default packageNamed: 'AST-Core')
And there is no category 'AST-Core'.
Moreover, I have just discovered that if I evaluate: RPackageOrganizer initialize. Then it appears :)
For example evaluate (RPackageOrganizer default packageNamed: 'RPackage-Core')
Saludos, Fernando
On Thu, Aug 9, 2012 at 12:24 PM, Mariano Martinez Peck <marianopeck@gmail.com<mailto:marianopeck@gmail.com>> wrote:
(MCWorkingCopy allManagers collect: [:p | p package name] ) includes: 'RPackage' -> true
(RPackageOrganizer default packageNamed: 'RPackage') -> KeyNotFound
bug?
-- Mariano http://marianopeck.wordpress.com
-- Mariano http://marianopeck.wordpress.com
On Aug 9, 2012, at 4:50 PM, Fernando Olivero wrote:
You're right! But notice that the RPackage logic of one to one mapping with categories, only breaks when it only provides extension methods as in the case of 'AST-Core' and 'RPackage'.
| p | p := RPackageOrganizer default packageNamed: 'AST-Core'. ( p extensionMethods size = 2 ) & ( p definedClasses size = 0 )
Only then, maybe this is a bug?
Yes Now just that you know. RPackage ****import**** (system -> rpackageOrganizer) was done with the idea that we would map a category to a package. Now we changed our mind, we will map a MCWorkingCopy to a RPAckage and categories will simply be class tags. So if you want to get rpackage working as the default MCWorkingCopy, you have to change the import phase or wait that we do it. Now we should sync with ben because nautilus may be confused (and do not show class tags). Stef
On Thu, Aug 9, 2012 at 1:52 PM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Thu, Aug 9, 2012 at 1:25 PM, Fernando Olivero <fernando.olivero@usi.ch<mailto:fernando.olivero@usi.ch>> wrote: Hi Mariano,
I've been using RPackage so i stumbled on the same "problem". RPackage maps System Categories (one to one), thus your problem happens because there's no category named 'RPackage'.
But for the rest it works. For example:
(RPackageOrganizer default packageNamed: 'AST-Core')
And there is no category 'AST-Core'.
Moreover, I have just discovered that if I evaluate: RPackageOrganizer initialize. Then it appears :)
For example evaluate (RPackageOrganizer default packageNamed: 'RPackage-Core')
Saludos, Fernando
On Thu, Aug 9, 2012 at 12:24 PM, Mariano Martinez Peck <marianopeck@gmail.com<mailto:marianopeck@gmail.com>> wrote:
(MCWorkingCopy allManagers collect: [:p | p package name] ) includes: 'RPackage' -> true
(RPackageOrganizer default packageNamed: 'RPackage') -> KeyNotFound
bug?
-- Mariano http://marianopeck.wordpress.com
-- Mariano http://marianopeck.wordpress.com
On Fri, Aug 10, 2012 at 9:18 AM, Stéphane Ducasse <stephane.ducasse@inria.fr
wrote:
On Aug 9, 2012, at 4:50 PM, Fernando Olivero wrote:
You're right! But notice that the RPackage logic of one to one mapping with categories, only breaks when it only provides extension methods as in the case of 'AST-Core' and 'RPackage'.
| p | p := RPackageOrganizer default packageNamed: 'AST-Core'. ( p extensionMethods size = 2 ) & ( p definedClasses size = 0 )
Only then, maybe this is a bug?
Yes Now just that you know. RPackage ****import**** (system -> rpackageOrganizer) was done with the idea that we would map a category to a package.
Now we changed our mind, we will map a MCWorkingCopy to a RPAckage and categories will simply be class tags.
So if you want to get rpackage working as the default MCWorkingCopy, you have to change the import phase or wait that we do it.
Now we should sync with ben because nautilus may be confused (and do not show class tags).
But the worse will be that Nautilus will show less packages, with more stuff :).
Stef
On Thu, Aug 9, 2012 at 1:52 PM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Thu, Aug 9, 2012 at 1:25 PM, Fernando Olivero <
fernando.olivero@usi.ch<mailto:fernando.olivero@usi.ch>> wrote:
Hi Mariano,
I've been using RPackage so i stumbled on the same "problem". RPackage maps System Categories (one to one), thus your problem happens because there's no category named 'RPackage'.
But for the rest it works. For example:
(RPackageOrganizer default packageNamed: 'AST-Core')
And there is no category 'AST-Core'.
Moreover, I have just discovered that if I evaluate: RPackageOrganizer initialize. Then it appears :)
For example evaluate (RPackageOrganizer default packageNamed: 'RPackage-Core')
Saludos, Fernando
On Thu, Aug 9, 2012 at 12:24 PM, Mariano Martinez Peck <marianopeck@gmail.com<mailto:marianopeck@gmail.com>> wrote:
(MCWorkingCopy allManagers collect: [:p | p package name] ) includes: 'RPackage' -> true
(RPackageOrganizer default packageNamed: 'RPackage') -> KeyNotFound
bug?
-- Mariano http://marianopeck.wordpress.com
-- Mariano http://marianopeck.wordpress.com
not if it is prepared :) On Aug 10, 2012, at 9:57 AM, Guillermo Polito <guillermopolito@gmail.com> wrote:
On Fri, Aug 10, 2012 at 9:18 AM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
On Aug 9, 2012, at 4:50 PM, Fernando Olivero wrote:
You're right! But notice that the RPackage logic of one to one mapping with categories, only breaks when it only provides extension methods as in the case of 'AST-Core' and 'RPackage'.
| p | p := RPackageOrganizer default packageNamed: 'AST-Core'. ( p extensionMethods size = 2 ) & ( p definedClasses size = 0 )
Only then, maybe this is a bug?
Yes Now just that you know. RPackage ****import**** (system -> rpackageOrganizer) was done with the idea that we would map a category to a package.
Now we changed our mind, we will map a MCWorkingCopy to a RPAckage and categories will simply be class tags.
So if you want to get rpackage working as the default MCWorkingCopy, you have to change the import phase or wait that we do it.
Now we should sync with ben because nautilus may be confused (and do not show class tags).
But the worse will be that Nautilus will show less packages, with more stuff :).
Stef
On Thu, Aug 9, 2012 at 1:52 PM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Thu, Aug 9, 2012 at 1:25 PM, Fernando Olivero <fernando.olivero@usi.ch<mailto:fernando.olivero@usi.ch>> wrote: Hi Mariano,
I've been using RPackage so i stumbled on the same "problem". RPackage maps System Categories (one to one), thus your problem happens because there's no category named 'RPackage'.
But for the rest it works. For example:
(RPackageOrganizer default packageNamed: 'AST-Core')
And there is no category 'AST-Core'.
Moreover, I have just discovered that if I evaluate: RPackageOrganizer initialize. Then it appears :)
For example evaluate (RPackageOrganizer default packageNamed: 'RPackage-Core')
Saludos, Fernando
On Thu, Aug 9, 2012 at 12:24 PM, Mariano Martinez Peck <marianopeck@gmail.com<mailto:marianopeck@gmail.com>> wrote:
(MCWorkingCopy allManagers collect: [:p | p package name] ) includes: 'RPackage' -> true
(RPackageOrganizer default packageNamed: 'RPackage') -> KeyNotFound
bug?
-- Mariano http://marianopeck.wordpress.com
-- Mariano http://marianopeck.wordpress.com
participants (4)
-
Esteban Lorenzano -
Fernando Olivero -
Guillermo Polito -
Stéphane Ducasse