Stop going to church and you'll run into a lot less of these whackjobs.
You had me at "don't read"!
Not very many people have ever dropped their DAW down the toilet.
I'll go have a peek at it now, see what's up.
But so does c++, that wasn't the actual problem.
Thank you, watching these links now.
init() should only ever be a thing where you need to perform some kind of init after construction. There's good cases for this in complex software e.g. where you need to run code after everything has been allocated / inited but not prior to some other thing.
CRYENGINE is full of classes that need an init call to complete, and even PostInit ().
The world is more complex than you think.
Multiple inheritance is a two edged sword. Used badly you will definitely cut yourself and others around you. Used right, it can be just the right tool.
There's *very few* times I'd consider using multiple inheritance instead of interface inheritance + 1 concrete inheritance. The only time in recent memory was for BOIDS. The existing code had chickens, turtles, eagles, fish and a few others. Turns out turtles inherited from chickens...yeh...anyway, the idea was that we'd go with standard classifications instead - terrestrial, aquatic and amphibian.
Obviously the chicken-turtles needed some rework to become amphibians instead.
Terrestrials should 'walk', avians should 'fly', 'aquatics should 'swim' and amphibians should 'walk+swim'...and really birds need to both walk and fly.
I left it up to a junior to sort it out, so hopefully it doesn't totally suck.
That is literally one of the only times I've ever though maybe multiple inheritance is a great idea. Yeh, I've wanted to use it to be lazy, but given all other factors....it's best left infrequently used.
I don't throw exceptions because I write games you insensitive clod!
I applied, but the recruiter insisted I already have five years experience in suicide bombing before he could get me a decent placement.
Add me to the list of kids who did this with the same result (OSI C1P - 6502 based CPU). I wrote quite a few games for myself back then...wish I still had the cassettes they were saved to. I wrote
* a "snake" game with two player mode
* a couple with two players using half the keyboard each to chase each other around
* one to drop torpedoes from a ship onto a sub controlled by the other player
* a 3D maze from first person perspective using only ASCII graphics
* space invader clone (assembler and never finished)
* car driving with winding track (assembler to push screen updates fast enough)
* text adventure games with verb noun commands
* and a bunch that I can't recall any more
I lived in a block of flats in the 90s and we had two computer programmers in our flat, and a couple of older guys with PC in a flat above and below ours...solution...run coax out the windows of ours and up / down to the other flats with a terminator at each end. We left it hooked up permanently to power our Warcraft I/II sessions and the occasional Doom / Quake / HL matches.
But sure enough, every so often we'd be like "hey, where's the network" only to find a neighbour had closed with windows and uncapped their end of the net. Time to break out the spare BNC endpoints and terminate their arses!
I'm still using the Nokia N73 I bought in 2006. It lasts about a week on a charge, but then again I don't really use it that often. I did have to replace the battery about 2 years back, but 7 years on a single battery seems fair enough. The only reason I'd give it up is the text on the screen is tiny and it's getting hard for my old bastard eyes to read it now.
Maybe you should try getting a second hand handset of ebay?
You didn't need to put all the utilities on it, just command.com was enough IIRC. Then, you'd keep a full DOS disk on hand for when you needed to run any of those pesky external utilities. Real men had two disk drives, so they didn't even need to swap the disk back and forth!
I used to do almost exactly the same thing, except the computer I had (OSI C1P) had a mode to enter hex codes into sequential memory locations one at a time. I'd write the code, hand assemble it to opcode, work out the jumps (pray I didn't make a mistake), then punch it in and JMP to the start location.
Eventually I saw a magazine article that showed how to write an assembler in BASIC for a similar sort of machine . Some quick hacking later I had a pretty decent line editor (my own work) and an assembler that handler the opcodes and jump calculation for my machine. It was pure bliss!