I think the definite book for Murphy and all other meta-"laws" is this one:[

Murphy's Law: Complete

](https://www.amazon.co.uk/Murphys-Law-Complete-Mandarin-Humour/dp/009944545X/ref=sr_1_6?s=books&ie=UTF8&qid=1518089322&sr=1-6&keywords=murphys+law)[^] It is fun, in any case!

OK, how does your 1 statement knock out codeline look like? Show, don't tell :-) !

I second that opinion. Let me as a old user with bad eyesight control how big the damn thing appears on my device. :thumbsup:

I'm all in for vacuum valves. They do not care too much about EMP... ENIAC, go!

I was 13 years old, back in 1973 (BASIC). However, I was 15 years before I actually could run my code - I didn't have access to any computer or even programable calculator before 1975. - But I miss those days... / Normann Aa. Nielsen

Call me old-fashioned or purist, but I do not see the need of adding more features to C. The beauty of the language is related to its simplicity, as the most common assembly language replacement available. Furthermore, many of the wishes and wants are found in C++ - so why not go there?

Do they then have to recompile the kernel of the space station each time a new astronaut is entering the ISS - or are they going to claim that the astronaut is not compatible because he is bashing around??? :confused:

How about: "Was that my phone? Oh, I better run and get it..."... :rolleyes:

Well, you may be a bit of a whiner, IMHO ... ;P There are 2 rules to remember here: 1. Don't !! 2. Wait !!! Thing is: In 2001 this is how we wrote that kind of code that you're complaining about. So there may be a large / huge amount of legacy-code that (fair enough) would have been so much nicer with the newer ways of doing it. But the code may actually work, as it is. Thus rule 1 above: 1. Don't == If It Ain't Broke Don't Fix It If the code does not work, then you must fix the problems, and in doing that you can do whatever is best But whait might be that you want to demonstrate better practies. No harm in that - just remember rule 2: 2. Wait == Do not do it yet, but wait to the proper time... Rule no. 2 is for experts only! The proper time could be a stand-alone project, or an isolated routine / module.

Well, for some folks that I know it should be fairly easy to save their consciousness on a old-time 180K single-sided floppy disk, even together with some interresting data. For most others I would say "No-way, José!" You may store a snapshot of all the neuronic activities for >clik< THIS moment, but we are really not sure whether that is enough - what about the chemical state, how about the framework (I understand that the brains are wired differently from person to person) and so on. And then there are the ethical / spiritual / practical problems... Much easier to rely on a divine intervention! :wtf: :wtf:

Wonderfull! Even to the point of paraphrasing the old BASIC error message "?Redo from start" - and so that we really can see it, duplicate it several times. Nice ;P

Ah, but it was Windows that started it. Nyah, nyah... ;P As for the two other points, they are still valid...

A wee bit of commmenting would be nice, but other than that I cannot see a problem here. As for porting to big-endian system: First of all, that will never happen. Secondly, there will be more places to fix if it did happen. Thirdly, the code is platform-restricted anyway (to Windows), so there is not a problem...:cool:

I was 16 in 1976 and had no money - I loooooooonged for the Imsai 8080. Luckily my gymnasium had a Nova 1200 from Data General, disguised as a RC7000 from the Danish company "Regnecentralen" - no disk, only punch tapes. Those were the days...

Crossing the bridge: You have to pay the dwarf: Give him the golden eggs (they will return to their original place if you utter the formula FEE FIE FOE FOO) and you can pass. When you go back, you bring the bear with you, that will scare him off.. (Why do I still remember such things? I last played Adventure in 1983, on a CDC Cyber mainframe)...

There is the "goto" in C# switch. That I have used lately. Otherwise I regard break and continue as instances of goto: break is the good guy (forwarding) where continue is the bad guy (backwarding(!)). / Normann

My selected few are (have known / are using): Rank 7/10: Visual Studio 2010 - using on job Rank 8/10: MetroWerk - have used on job Rank 7/10: MinGW gcc - using privately Rank 9/10: Borland C++ - have used privately (long time ago) Hope this is what you want Regards, Normann

Keep the books with general knowledge in them, for example mathematics (how to do Hamiltonian Quadruple, Laplace transformations whatever...), computer science (architectonial secrets of operating systems now forgotten) and so on. Thy rule should be: He who forgets the past is bound to repeat it...

Short and to the point...

That figures! The cost of consumables is way too high, and the added software locks on the cartridges (making sure that it is not easy to just pour in some 3rd party ink into them) it annoying. There is something not healthy when I find it cheaper to buy a completely new printer that a new cartridge...