yes this is a fun rule. Now you have to have a common ancestor or a package entry point. Stef On Jun 6, 2012, at 11:55 PM, Igor Stasenko wrote:
Yeah..
we even can make a lint rule: - 1 max reference per package to class from another package unless referencing class belongs to kernel
modules.. they are so easy to do, if everyone would follow that rule :)
On 6 June 2012 22:54, Guillermo Polito <guillermopolito@gmail.com> wrote:
Steph wants less hardcoded references to PackageInfo :)
On Wed, Jun 6, 2012 at 10:51 PM, Martin Dias <tinchodias@gmail.com> wrote:
Hmm I didn't catch it
Martin
On Wed, Jun 6, 2012 at 4:47 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
ok for me I'm studying PackageInfo and the rest to see what I can do.
mariano/martin
I would like to extract PakageInfo into self packageInfo in the fuel code.
Yes, I like that the idea. I guess you are talking about FuelPackageLoader in #named: and #withPacakges: right? What about calling it direclty #package? so that we may be able to change it later to PackageInfo or RPackage or whatever?
Can I do it?
Stef
-- Mariano http://marianopeck.wordpress.com
-- Best regards, Igor Stasenko.