> I would interpret that reason for "globals being bad" as being because > it provides uncontrolled access to variables - the same evil as making > member variables public to avoid having to write and use Get/Set > methods as some people do. To me, having system objects global doesn't > 'encourage' as much abuse as plain variables.
Exactly. This is done for the sake of maintaining the 'encapsulation'. But read the articles I pointed to in another message to see how globals can in fact improve encapsulation. The point you suggest above is a non-issue if your global object is an instance of a class with a well designed interface and correct encapsulation techniques. ------------- Ehsan Akhgari Farda Technology (www.farda-tech.com) List Owner: [EMAIL PROTECTED] [ Email: [EMAIL PROTECTED] ] [ WWW: http://www.beginthread.com/Ehsan ] "Steps taken forwards, but sleepwalking back again..." - High hopes, Pink Floyd
