|
Maybe that was in the day where templates, exceptions, and RTTI had enough overhead that Embedded C++ didn't support them. Their overhead is probably still too much for a toaster, but they shouldn't be a problem in most of today's systems.
|
|
|
|
|
Did they also try to rewrite the Linux kernel? Linus Torvalds on C++[^]. 
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
There were dozens of Unixes before Linux! I remember one gathering of representatives for different Unix variants (I didn't participate - I was still a student then) when it was remarked that they were missing one variant: There were 31 of them. Then someone pointed out that computer guys love to start counting from zero, so 31 is actually a rounder number than 32 
My memory is not able to date this, relative to the arrival of C++. Maybe C++ wasn't a viable alternative at that time. But quite a few of those 31 Unix variants lived for many years after C++ became popular - a few are alive even today.
It took quite a few years for Linux to grow from a "toy
|
|
|
|
|
Duplicate (truncated) post? Enjoyed the full version.
Paul Sanders.
"Life is a minestrone" - which I take to mean that it's full of different bits and you should try to savour them all. I think that's pretty neat, I like that analogy.
And if you don't mind, here's a quick plug for my little one-man business. Follow the link if you're interested in ripping your vinyl collection: www.alpinesoft.co.uk. Thanks.
|
|
|
|
|
I did, by accident hit some key (don't know which one) that took me away from the 'Reply' page. So I hit 'back' (aka. Alt-Left) to get back to continue editing without noticing that the unfinished entry had been posted - not until you point it out.
I could delete the unfinished entry, but that would leave your reply orphaned. So I leave it in. I have made worse blunders 
|
|
|
|
|
There were dozens of Unixes before Linux! I remember one gathering of representatives for different Unix variants (I didn't participate - I was still a student then) when it was remarked that they were missing one variant: There were 31 of them. Then someone pointed out that computer guys love to start counting from zero, so 31 is actually a rounder number than 32
My memory is not able to date this, relative to the arrival of C++. Maybe C++ wasn't a viable alternative at that time. But quite a few of those 31 Unix variants lived for many years after C++ became popular - a few are alive even today.
It took quite a few years for Linux to grow from a "toy" clone to become even a significant competitor to the non-FOSS Unix variants, and even longer to become the dominant *nix. I, too, have heard about these proposals to rewrite Unix (not Linux) in C++. It is so long ago that Linux was far away from the dominance it has today.
Another thing is that although we may be entertained by Linus' rant, this style of arguing (which is not atypical for the source ...) is part of the reason why Linux was not taken to be a "serious" OS in its first years. (Note that the rants are 15-18 years old.)
|
|
|
|
|
CPallini wrote: Did they also try to rewrite the Linux kernel [in C++]?
Hope not!
Paul Sanders.
"Life is a minestrone" - which I take to mean that it's full of different bits and you should try to savour them all. I think that's pretty neat, I like that analogy.
And if you don't mind, here's a quick plug for my little one-man business. Follow the link if you're interested in ripping your vinyl collection: www.alpinesoft.co.uk. Thanks.
|
|
|
|
|
I don't think so, you know what they say,
They: Hare today, gone tomorrow...
I'll get my coat.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Yes, do
Paul Sanders.
"Life is a minestrone" - which I take to mean that it's full of different bits and you should try to savour them all. I think that's pretty neat, I like that analogy.
And if you don't mind, here's a quick plug for my little one-man business. Follow the link if you're interested in ripping your vinyl collection: www.alpinesoft.co.uk. Thanks.
|
|
|
|
|
Were I to learn a new language, it would likely be D.
Unfortunately, my boss wants me to learn Python. 
|
|
|
|
|
Today I am staring at two implementations of a DMA enabled I2S parallel bus system trying to make sense of them since they are using very scarcely documented registers and I'm totally new to this.
I'm tackling this *because* I can't do it.
I tackled LL, LALR, and eventually GLR parsing *because* I couldn't do it.
Challenging myself is not only how I make wicked code, it's how I level up. It also keeps me engaged.
I don't always succeed, but most of the time I do, and often times when I don't I'll come back a month or sometimes even years after I put it down, dust it off, and make it dance.
There's a certain safety in sticking with what you know, and a lot of times in the professional realm, that's the prudent approach.
But I don't feel like you grow as much in terms of the craft. It gets to be habit, and empty repetition.
To err is human. Fortune favors the monsters.
|
|
|
|
|
You're not only a good coder but a prolific writer.
You have a knack for writing that I don't have, I don't express myself very well and it takes forever for me to document a project for my site.
The less you need, the more you have.
Even a blind squirrel gets a nut...occasionally.
JaxCoder.com
|
|
|
|
|
Same here Mike, the documentation ( when I'm made to do it ) takes me longer than the programming.
"Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
I hear ya. I start out and try to get everything just so and as I get further into it I lose interest and just rush through, so the beginnings are half way decent but the further you read the more convoluted it becomes.
The less you need, the more you have.
Even a blind squirrel gets a nut...occasionally.
JaxCoder.com
|
|
|
|
|
This might be a situation like TDD where it's a lot less overwhelming if you do it as you go.
One thing I do in visual studio when I'm working professionally, or at least on an involved open source offering, is I mark warnings as errors in release builds and also tell it to generate docs from doc comments.
That way any publicly exposed methods that don't have doc comments on them get flagged as errors under the release builds.
It's a start.
But honestly, just try writing a technical article about your code. It doesn't have to be good - you might be the only reader of it.
But with it, you can generate an outline, and with that a table of contents.
Failing that, you can go through the header files and start your outline with the name of each, before drilling down into them. If you already divide your source code out into multiple files as a matter of course this can work pretty well in terms of getting you started.
And if you're not great at writing, write samples. Lean on that. A little bit of verbiage with a lot of example code.
I hope some of that helps.
To err is human. Fortune favors the monsters.
|
|
|
|
|
Thanks for the advic.
The less you need, the more you have.
Even a blind squirrel gets a nut...occasionally.
JaxCoder.com
|
|
|
|
|
I was kind of a writer first. I wound up being part of "Young Authors" twice, I could have seen getting an English or a degree in literature as easily as I got into coding if things had played out differently. I learned to read when I was 3, and was voracious about it for a long time. I think picking up literacy early sort of wired me for writing. Audre Lorde (activist, poet) also learned to read at 3, although she was a better writer than I am. Still my point is, I think training young is what does it, and the younger you can do it, the easier is is when you get older. I could be wrong. Maybe we're wired a certain way and that leads to early literacy and a knack for writing. Causality in matters like that can get slippery fast.
Either way, the gift really helps when it comes to documenting what I've coded. I feel blessed for it.
To err is human. Fortune favors the monsters.
|
|
|
|
|
I have attention problems, but I'm getting better.
I have become a voracious reader, I've probably read 70-80 books this year and I've got many more lined up.
My writing is getting better, at least I think so, but it's so hard to get going.
I'm finding that many folks can write but few are really good at it.
The less you need, the more you have.
Even a blind squirrel gets a nut...occasionally.
JaxCoder.com
|
|
|
|
|
I don’t understand what you are trying to say here…
🤪
If you can't laugh at yourself - ask me and I will do it for you.
|
|
|
|
|
"We choose to go to the moon and do the other things, not because they're easy, but because they are hard."
|
|
|
|
|
No pain, no gain... sorry for cliche but mostly true.
Reading is like breathing for the brain and writing is somewhat similar but comes later.
Without it, life is cruel.
Most people in US prisons are functionally illiterate.
|
|
|
|
|
To be adventurous or to be prudent?
Be adventurous about what you discover and prudent about what you implement.
If you discover a better less error prone path then it could be prudent to implement it.
|
|
|
|
|
That doesn't work for me when I'm learning though, because I learn by doing, which means I'll implement something well before I realize I understand it, and that process helps me understand it further. The implementation I'm left with generally needs some retooling but that's how it goes. 
To err is human. Fortune favors the monsters.
|
|
|
|
|
I learn by doing to and I have an enormous codebase of fantastical experimental ideas from which I have learned a lot but would not employ in production code. Having said that, I am retired now and can afford to be wise and circumspect. In fact I specialise in it because it is less stressful.
Back in the day though, I used to innovate wildly and put it straight out in the field because it was needed. I had a lot of confidence in what I was doing but it did mean that I had to become an expert at completely refactoring my own innovations without breaking anything - usually because I hit a design cul-de-sac tying up loose ends. Yes, you do have to roll up your sleeves, get your hands dirty and have confidence in your own brilliant ideas. I still do it but I now have the luxury of only publishing what I want to when I think it is ready.
|
|
|
|
|
I believe that when I stop growing, I stop living. Even breaks from direct learning can provide growth just as rest periods are when the muscles grow when weight training.
I can always find ways to grow, even in an environment where I'm working with what I know, but absolutely new things are a delight to learn, it's true.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
