Re: What is your opinion on Global Objects?

[Hubert <herrdoktor@fumanchu.com>]

> A database connection is not; you will need to copy the database from
> one object to another when you change the schema or move to a new
> backend in the future.
>
Yes my application is a little different from what most of you probably 
work on. Like I said, I am working on a multiplayer game and the things 
that are implemented as singletons here exist absolutely only once.

The reason for my question was not so much for my actual work but for 
future subprojects we will be doing where we want to attempt a different 
approach to the design, with more upfront planning and a scheme that is 
more like Structured Design, but with elements that allow for OOP 
elements, so we can't just take the old books by Yourdon et al and apply 
their technique, since we can't deny that there is value in small scale 
inheritance sometimes yet the techniques and diagrams for Structured 
Design don't take that into account since they are mostly from the 70s 
and 80s.

Anyway thanks a lot everybody for the input, I didn't think of global 
objects as subprogram calls with internal status variables before since 
I am kind of preoccupied with C++ thinking and look at most everything 
as a self sufficient object, so it's good to get a different perspective.


---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com