While you are at it, write it in machine code, too? That seems to be in-line with your goal of intentionally making your life harder.
While you are at it, write it in machine code, too? That seems to be in-line with your goal of intentionally making your life harder.
Way back in the "good old days"... I actually did some programming with front panel switches ( Like this ) so by comparison, C is a breeze...Originally Posted by cyberfish
Wow, that makes my first computer look super advanced.
C+/- programmer extraordinaire
hmm... wasn't there a joke about how Bill Gates and Paul Allan were actually able to make Altair 8800 harder to program when they created BASIC with it? I can't quite put my finger on it (can't remember the exact wording) but it was quite funny and seemed to indicate that this was a rather easy micro-computer to program until they created BASIC.
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
Oh i don't know the joke... But, I'd say having to manually key in a 64byte loader from the switches --set binary switch pattern; load accumulator; set switches; load accumulator, and on and on-- then insert a cassette tape and press run... just to load a 1k program that simply flashed the front panel lights was pretty much as primative as it gets...
Yep... a lot of development went on between those two machines...
My first "real" computer was one of THESE It eventually got me the job servicing THESE and it got me started as the national service manager for THIS LINE. From there it was PC-Clones then as the market progressed I moved to the stuff we use now and finally on to Home Theatre setups... returning to my first love: audio systems. And now... retirement with a dab of C coding tossed in for interest.
Your code style is hardly no better than newbies who do not indent at all. Ergo, it is a bad code style.
What you ultimately use is up to you, just don't expect me to read it. And nature help anyone else who has to.
Why do you insist on writing all yourself? If there is something already written, use it.Why would I look for another library? I already wrote one... It's all nicely tucked away as a .lib file I can use any time I need it.
If it isn't enough for you, then write a wrapper around it.
You had to get all low and dirty with unicode because you just couldn't use a third-party library.
I tend to reinvent the wheel sometimes myself, but this is madness.
Wrong libraryMoreover, it's far more successful than the IsTextUnicode() call in WinApi... theirs got about half the files I was working with wrong... mine hasn't missed yet and it goes the extra bit of actually translating the text to wchar_t (UTF16LE) for me.
Stop relying on WinApi. For unicode, it's not going to cut it.
Yeah well, what can I say?I dunno, Elysia, you seem bent upon using 3rd party libraries for everything. I've never used one yet (except to mess around with). I actually enjoy the challenges of writing my own .lib files...
Should I write my own classes for every little thing I use? Should I write my own vector, map, smart pointer, copy algorithms, etc, etc, etc? Far too time consuming. Better use what tools are available to me and save my strength on implementing things for which there is no tool that meets my requirements.
Given the attitude... all I can say is "thank you".
Why write my own stuff? Experience, knowledge, practice, insight... Whatever you call it, it's a part of craftsmanship I particularly enjoy.Why do you insist on writing all yourself? If there is something already written, use it.
If it isn't enough for you, then write a wrapper around it.
You had to get all low and dirty with unicode because you just couldn't use a third-party library.
I tend to reinvent the wheel sometimes myself, but this is madness.
Way back when I started with computers, my first machine was a KIT... bags of parts, bare circuit boards and an empty chassis... My first color television set was a KIT, so was my first ham radio set... I haven't purchased an audio amplifier since the mid-1970s, what I need I design and buld for myself ...It's all about knowing the tech you deal with.
And I could just as easily advise you to stop running away from it...Wrong library
Stop relying on WinApi. For unicode, it's not going to cut it.
I don't know why this bothers you so much but you really do need to get over it.
Ok... but you're missing half the fun!Should I write my own classes for every little thing I use? Should I write my own vector, map, smart pointer, copy algorithms, etc, etc, etc? Far too time consuming. Better use what tools are available to me and save my strength on implementing things for which there is no tool that meets my requirements.
I tend to write a lot of algorithms... And I do frequently implement a lot of stuff, such as Database classes.
Just not unicode. That's madness, and IMO, a waste of time.
But you know... I do low-level stuff sometimes. I just don't embrace it with open arms.
Now there's an understatement if I ever saw one.
Based on your other postings, here and in different threads, I'd have to conclude you find it seriously repellent and are on some kind of blood-quest to stop people from using it. Seriuosly, you are so over the top on this it's downright scarey...
I study operating systems right now because I find it interesting. That doesn't exactly strike you as the type who hates low-level stuff, does it?
I find it fun to think about how to abstract OS code into safe high-level and type-safe code with a language such as C++, as much as possible.
That is my philosophy.
