Oh god frnash, that's over the top. On that note have a good summer.


BTW, been taking some C++ classes at the local college. Don't have a good grasp of pointers. Any good resources out there?
I wasn't that impressed with C++ vs. plain ol' "C" language. C++ is all about "
object-oriented programming", thus
objects, and most of the early developers didn't have a clue.
As a result, there were many too-hasty C++ implementations, without a rigorous, careful ground-up hierarchical design, which were thus nearly impossible to maintain; worse than the ol' "spaghetti code" Basic programming of yore. That brings to mind an old truism from my programming days:
"You will never have enough time to 'do it right the first time', but you will have plenty of time to fix a hasty implementation — after the product ships!"
So what's an "object"? The short answer, in 25, er… 100 words or less:
An "
object" is a concrete "instance" of a conceptual "
class" (blueprint) that encapsulates both its own
data types and the
methods for manipulating those data types, as opposed to the historical method of manipulating data with external "methods" (programs, subroutines). This has the effect of "hiding" that data (
data encapsulation) and restricting the "methods" — that may be used in accessing and/or manipulating that data — to those methods embedded in the object, in attempt to protect that data from unintended effects.
That being said, what specifically is the problem you are having with pointers? (Feel free to send me a PM, prefereably including your email address, and we can deal with this off-line.)