Thanks Max! those are CAN DO! type answers.
I remember the baby fit Dr. Richard Mueller (my Uncle who worked for Control Data Corp.) threw when Pascal came out and then was discovered to be more than a teaching tool. He had much the same idea, but sat on it too long because he couldn't see it resulting in millions of dollars for his company right away. Dick, like many talented programmers could be... well, let's not call him unreasonable!... let's just say while never wrong, sometimes he was less right than he could be!
At the time I thought he was kinda an idiot for thinking it wouldn't go farther. After all, programming built to explore possibililities stands half a chance of getting you just that; possibilities!
I know what you mean by going 30 years into something and still feeling like a novice. When people ask me my level of understanding of the IL-2 series of games, I tell them I'm still a novice! I know that by most folks definition, this simply isn't true. But I'm smart enough to stay dumb enough about what I've learned to stay on the learning curve. I truly believe this is what keeps us growing and I've always felt we are either growing or dying. I'm sure this community has seen me do both!
I almost didn't even mention these efforts to this community because of the natural rection I'd get. I stumbled upon 3 programmers who work on the flight simulator over at Lockheed. They gave a funny and relatively accurate definition of us flight sim fans....
Middle aged men who appear outwardly to be otherwise normal and of at least slightly above average intelligence who only become psychotic when dealing with flight sims or anything else aviation!
They discussed with me using Pascal to do things, but felt I'd be going a bit too far the radical route by punching in Pascal. They said C++ is the way to go NOT because it is the most capable, but because it will do what I want it to do and will not result in a code so odd in its application that those joining on the project later would have to go through a 3 year learning curve just to understand the basics of what I was doing.
Now, I have no plans to single handedly punch the entire code. I plan on doing the part that none of the others seem to be able to get their collective brains around and that's the physics engine for the game. I sent the link to one of the Lockheed guys and he said by the time I ripped apart and strung that code back together enough times to get it to do what I want it to do, I'd be better off just going from jump. Who knows, maybe I can at least use it enough to help me learn and then proceed from there.
Tell you what, let's not make grand plans for now. Let's just say for reasons not fully understood or explained, Luckyboy wants to learn C++. We'll see what I can learn in a year and oh, by the way, I just got a job offer from a Company that after a year of working for them will be willing to PAY for me to go to school and learn C++ formally. Like I say though, who knows what's next in life. I simply want to grow because I'm sick of dying slowly. there's a line from the movie "The Shawshank Redemption" that says...
Get busy living, or get busy dying!