Using prefixes/suffixes is a time-honoured hack (and I use it myself,
mostly for Rb5.2 compatible plugins) but although it helps avoid
collisions, it pollutes the namesapce just the same - it's just that
the slick is more self-contained ;)
Using 1 module name in global space is far better than 30 methods
that use the same prefix IMHO, and this works brilliantly in Rb5.5 so
you can't go blaming plugin developers if Rb2005 has broken this
behaviour.
Frank.
–––––––––––––––––––––––––––––––––
Open Source RB Goodies and Shareware
<http://developer.chaoticbox.com/>
<http://www.chaoticbox.com/>
–––––––––––––––––––––––––––––––––
On 5-Dec-05, at 1:35 AM, Brad Hutchings wrote:
Right. But developers can be considerate of others in how they
pollute the global namespace. That's the axe I was subtly
grinding ;-). In other words, if you are declaring global anything
in your plugin, prepend or append it with a short mnemonic that
identifies the source. Developers (especially plugin developers)
who claim that their naming collisions are REAL's fault for not
have namespaces are copping out and just causing problems for
everyone else. OK, axe ground, back to work.
On Dec 4, 2005, at 10:28 PM, Frank Condello wrote:
In Rb 2005 you're going to pollute the global namespace no matter
what: <http://www.realsoftware.com/feedback/viewreport.php?
reportid=acfhivpw>
Then there are times where using a namespace would be nice but
it's not possible to extend it with Rb code, so globals (or nasty
hacks) are your only alternatives: <http://www.realsoftware.com/
feedback/viewreport.php?reportid=agwxxgcl>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|