I think that we missing a way to determine to which package some
global belongs to.
When you loading a package it can declare new global, but there is no
reflective mechanisms in system to tell, to which package it belongs.
If we could have that, then clearly, if you serialize the package,
we should try to reduce their number. I like newspeak solution to this regard.
Stef
Igor Stasenko wrote
I think that we missing a way to determine to which package some
global belongs to.
When you loading a package it can declare new global, but there is no
reflective mechanisms in system to tell, to which package it belongs.
If we could have that, then clearly, if you
Mariano,
Rejecting all classes and traits might give you global variables.
Smalltalk globals size. 2188
(Smalltalk globals copyWithoutAll: Smalltalk allClasses) size. 95
((Smalltalk globals copyWithoutAll: Smalltalk allClasses) copyWithoutAll:
Smalltalk allTraits) size. 14
Regards,
HwaJong
Hi guys. In Fuel, we need to identity which globals present in Smalltalk
globals are NOT classes or traits, because we need to manage them as
globals. So far we have a hardcoded list:
defaultGlobalSymbols
^ #(#Smalltalk #SourceFiles #Transcript #Undeclared #Display
#TextConstants
Am 2012-04-17 um 12:50 schrieb Mariano Martinez Peck:
Hi guys. In Fuel, we need to identity which globals present in Smalltalk
globals are NOT classes or traits, because we need to manage them as globals.
So far we have a hardcoded list:
defaultGlobalSymbols
^ #(#Smalltalk
Be careful that #isBehavior is false for Traits :). To fix I think.
On Tue, Apr 17, 2012 at 1:41 PM, Tobias Pape das.li...@gmx.de wrote:
Am 2012-04-17 um 12:50 schrieb Mariano Martinez Peck:
Hi guys. In Fuel, we need to identity which globals present in Smalltalk
globals are NOT classes
Am 2012-04-17 um 15:20 schrieb Guillermo Polito:
Be careful that #isBehavior is false for Traits :). To fix I think.
oO
I did not expect that.
However, I think Traits should respond with true to traits.
Well then…
1) send isTrait, if applicable
defaultGlobalSymbols
^ (self environment or
On Tue, Apr 17, 2012 at 3:50 AM, Mariano Martinez Peck
marianop...@gmail.com wrote:
Hi guys. In Fuel, we need to identity which globals present in Smalltalk
globals are NOT classes or traits, because we need to manage them as
globals. So far we have a hardcoded list:
defaultGlobalSymbols
I think that we missing a way to determine to which package some
global belongs to.
When you loading a package it can declare new global, but there is no
reflective mechanisms in system to tell, to which package it belongs.
If we could have that, then clearly, if you serialize the package, you
On Tue, Apr 17, 2012 at 10:11 AM, Igor Stasenko siguc...@gmail.com wrote:
I think that we missing a way to determine to which package some
global belongs to.
When you loading a package it can declare new global, but there is no
reflective mechanisms in system to tell, to which package it
On 17 April 2012 18:52, Eliot Miranda eliot.mira...@gmail.com wrote:
On Tue, Apr 17, 2012 at 10:11 AM, Igor Stasenko siguc...@gmail.com wrote:
I think that we missing a way to determine to which package some
global belongs to.
When you loading a package it can declare new global, but there
12 matches
Mail list logo
