The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Actually, I didn't look that far down - thanks for pointing it out.
Nor did I notice that this web page claims that it is Hell, Michigan. It is not, it is Hell, Norway.
(For those who have gone by air to Værnes Airport, Hell is the village next to it.)
The style of the sign is distincly Norwegian, European, rather than American.
I drive past it regularly; it certainly has been frozen over this way quite a few times.
The Norwegian name Hell has no relationship to Helvete, but comes from "helle" or "heller".
A "helle" is a flat stone, like a slab of slate, or any stone that is "flat", or even a flat surface on a large stone that is not so flat.
A "heller" is a stone that sticks out from a mountain so that it serves as a shield against rain and snow. In the stone age (and even hunters in more modern times) could make a dwelling under a "heller". This is probably the origin of the name of the place, being much older than Christianity and its hell, certainly in Norway, but the name may be as old as Christianity itself.
For the place outside Bergen, called Paradis, there is no similar old explanation; that is a Christian name. Unfortunately, the train stop at Paradis was closed down several years ago, so you no longer can buy a train ticket from Paradis to Hell, or from Hell to Paradis. I suspect that quite a few of those tickets were never used.
Hell - Gods-Expedition[^] uses a 100+ year old spelling for "cargo handling" ("gods", cargo, is unchanged, but today we write "ekspedisjon"), but everybody loves the old sign, so they will probably keep it for another hundred years...
I am so old that I remember when we made printouts of our source code. Several of the printers I used placed the underscore so low down - I guess that it shouldn't interfere with the descenders of lower case letters - that it visually certainly did not tie together the parts making up the identifier.
We even had zebra paper in my first years as a programmer, ane when the underscores from the white lines printed halfway into the top of the grey line, they were very easy to overlook, especially in identifiers starting or ending with an underscore.
Ah ... implicit typing. One of the delights of FORTRAN. Along with COMMON which allowed you to declare a single character variable and use it as a three dimensional array of integers. Handy for OS mods on GEC 4070's as I recall.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
for each additional k value i need to add a thirdSym, fourthSym, and accompanying nested ifs.
Meanwhile, if I rewrite this as a state machine I can use gotos, and then recycle similar paths.
This is really hard to show you an example of because the result is spaghetti but it's easy to generate programmatically, or to graph visually. (i don't want to break out graphviz right now though - it's late)
However, being able to recycle those paths as they converge can dramatically reduce the amount of code you need, but you have to be able to bounce between the different branches, the way an if won't.
You can do similar using goto case albeit less efficiently than a goto based baked state machine overall.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
Last Visit: 24-Feb-20 20:09 Last Update: 24-Feb-20 20:09