|
Stone tools.
Flint is sharp, and easy to work (if you know how).
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: (if you know how)
You mean a smith would
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
|
|
|
|
|
Well, maybe: Knapping - Wikipedia[^]
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
You can make an even cruder hammer out of a large stone.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Are you saying Obelix was a smith and carrying a hammer on his back all day? (when he wasn't throwing it at romans)
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
|
|
|
|
|
He used to mostly throw Romans at Romans!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
You can, but it wouldn't be a lot of use for metalwork: stone is too brittle and liable to fracture with heating.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Just grab any tool. After all, every tool has a hammer side.
Kelly Herald
Software Developer
|
|
|
|
|
Bottom donkey - trendy killer (8)
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Bottom donkey -> ASS
trendy -> hip -> ASS
trendy -> IN =============================
trendy killer - overall
ASSASSIN
|
|
|
|
|
You are up tomorrow!
You could have made it easier for yourself though:
Bottom ASS
Donkey ASS
Trendy IN
Killer:
ASSASSIN
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Please may I steal this to use in the Discworld MUD? I want to graffiti the assassins guild...
|
|
|
|
|
Help yourself!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Disregarding the flagrant violation of protocol, and the total disregard of the red text at the top of the forum, those of you who have programmed in C++, have you ever used protected and private inheritance? I've never had a use for it, but have been extremely curious about when they are handy. They are not in C# (from what I've read), but maybe I've overlooked something, and they are useful in ways I don't know? Your thoughts and experiences, to expand an undeveloped understanding...
|
|
|
|
|
I never used protected or private inheritance.
Anyway, I reckon they could be useful.
|
|
|
|
|
The first time I read about them (years ago), they made no sense to me. The last reading I did made them seem like protected inheritance made public members protected , and private inheritance made public members private in the derived class. I can see this maybe being useful in some situations, but am curious as to where that would be the case.
|
|
|
|
|
I suppose they could have use, for instance, in implementing a Facade design pattern.
|
|
|
|
|
All members of the base class get restricted to the inheritance type. So both public and protected members of the base class are now private in the derived class if using private inheritance. So any users of that derived class don't "see" the inheritance. As I said in my other post, I've never seen a good example of why this would be needed though
EDIT: Two words for clarity. Also private base class members are still not visible to the derived class iirc.
|
|
|
|
|
I'm not a regular C++ dev but I've never had a reason to use them so far. I've also never seen a good example of why they're useful that can't be solved in another way (e.g. composition). Whether you value it or not is up to you and the situation, but it's worth mentioning that private and protected inheritance breaks the Liskov Substitution Principle, and private inheritance breaks polymorphism in the inheritance hierarchy.
Honestly though, I'd love to see an example of either being useful.
|
|
|
|
|
Well,
If you ever get to work at a company with thousands of developers (or as a program manager) you'll quickly understand the value. They are a very useful tool for controlling the application binary interface[^].
Let's say that you create an awesome library called DoSomethingAwesome.lib and everybody at your company wants to use DoSomethingAwesome. They take your lib as a dependency and quickly integrate it into dozens of projects. They derive classes from your headers and extend them and now it's DoSomethingMoreAwesome.
Then your team changes some of the internals and DoSomethingAwesome is no longer compatible with DoSomethingMoreAwesome. In fact now dozens of other teams at the company are having to re-write parts of their code to accommodate for the changes in your lib. Paying software engineers is expensive and now this change has cost the company thousands of dollars.
The concept of protected and private inheritance is a useful tool that allows the library development team to control the public interfaces and keep a stable ABI. It's just a tool in the toolbox.
Best Wishes,
-David Delaune
|
|
|
|
|
Thank you Very Much for this explanation! As I said before, I am in awe of your talents, and this is helpful for my understanding!
|
|
|
|
|
|
The abbreviation is overused, but lol!
|
|
|
|
|
(And also made me a bit sad, that we are overwriting the lives of other species to supposedly improve our own.)
|
|
|
|
|
Yeah,
David O'Neil wrote: we are overwriting the lives of other species to supposedly improve our own One of my old coworkers has a wife that was working as a research scientist at the Tulane National Primate Research Center |[^] and she would describe some of her research. They have over 5,000 primates, you have absolutely no idea... what she was telling me was worse than anything you can possibly even imagine.
Best Wishes,
-David Delaune
|
|
|
|