Segmentation Fault (core dumped)

[Kenneth Brody]

If you don't know much about C yet, please try not to volunteer
"answers" to other newbies' questions. You will be wrong, and other
people in the newsgroup will have to spend extra time un-confusing
the newbie. Don't worry, there will always be other newbies --- so
you don't need to jump all over yourself to respond to each one.
You can afford to wait until you know the language better.

[...]

On the other hand, posting "wrong" answers will be quickly corrected,
as long as they are C related. (One of the reasons that keeps getting
pointed out as to why you shouldn't give OT answers to OT questions,
without at least pointing them somewhere they can be on-topic -- the
fact that posters here can't necessarily correct "wrong" answers as
this.)

Also, it's not just newbies that post "wrong" answers. I have been
programming in C for over 20 years, and I have been corrected here
on more than one occasion, when I posted an answer based on what I
"learned" 20 years ago, and which turned out to be wrong.

Besides, now Zack's misconception won't get in the way in the future.

However, I do agree that newbies should take their time before
making such bold answers. (Though it is a bit of a Catch-22, since
no one would have corrected Zack's misconception had he not posted.)

--
+-------------------------+--------------------+-----------------------+
| Kenneth J. Brody | www.hvcomputer.com | #include |
| kenbrody/at\spamcop.net | www.fptech.com | <std_disclaimer.h> |
+-------------------------+--------------------+-----------------------+
Don't e-mail me at: <mailto:[email protected]>

 

[Default User]

"Arthur J. O'Dwyer" wrote:

On the other hand, posting "wrong" answers will be quickly corrected,
as long as they are C related.

My recommendation is for the less experienced participants to answer
the question in their heads, then compare with the posted answers. If
there's a major difference, and it's not clear why, then ask about it.




Brian

 

[Joe Wright]

DanielJohnson said:



No, but it's "best of breed".


Clarity of thought is the best debugger there is. I've spent way too
much time stepping uselessly through code, one line at a time. A penny
of brainwork is worth a pound of code-stepping.

And depending on when you started, this could be 240 to 1.

On my first trip to England, about 40 years ago now, a pint of bitter
cost one and six. A tot of gin with tonic was two shillings. Those were
the days.

Twelve pence to the shilling, twenty shillings to the Pound. As I recall
a Pound cost about five Dollars US. Those were the days.

I haven't been back to the UK for thirty years now. What does a pint of
bitter cost today?

Here in Washington, DC a drink (even beer) will average five to six
dollars today in nicer places. Two dollars is about as low as you can go.

Do y'all still drive on the 'wrong' side of the road? Why is that?

 

[Richard Heathfield]

Joe Wright said:

I haven't been back to the UK for thirty years now. What does a pint
of bitter cost today?

A couple of quid (about four bucks, I think).

Here in Washington, DC a drink (even beer) will average five to six
dollars today in nicer places. Two dollars is about as low as you can
go.

Do y'all still drive on the 'wrong' side of the road?

Nobody here drives on the wrong side of the road, except when overtaking
or when risking the wrath of the law (and society at large) by driving
home from spending a tenner in the pub...

Why is that?

Well, if you're asking why we drive on the proper - i.e. the left - side
of the road, the answer is simple: if the driver of the oncoming
vehicle attacks you, you want him on your right, because that's the
side on which your sword will be most effective (if, like most people,
you're right-handed). You can use the other hand to control the horses.

 

[Richard Tobin]

Well, if you're asking why we drive on the proper - i.e. the left - side
of the road, the answer is simple: if the driver of the oncoming
vehicle attacks you, you want him on your right, because that's the
side on which your sword will be most effective (if, like most people,
you're right-handed).

I knew there was a reason I never learnt to drive.

-- Richard

 

[DanielJohnson]

Joe Wright said:



A couple of quid (about four bucks, I think).



Nobody here drives on the wrong side of the road, except when overtaking
or when risking the wrath of the law (and society at large) by driving
home from spending a tenner in the pub...


Well, if you're asking why we drive on the proper - i.e. the left - side
of the road, the answer is simple: if the driver of the oncoming
vehicle attacks you, you want him on your right, because that's the
side on which your sword will be most effective (if, like most people,
you're right-handed). You can use the other hand to control the horses.

I came across this link on wikipedia about left and right hand
driving. I visited UK this December and was pleasantly surprised to ee
the traffic the other way but in couple of days I think I could
adjust.

http://en.wikipedia.org/wiki/Driving_on_the_left_or_right

Daniel

http://en.wikipedia.org/wiki/Driving_on_the_left_or_right

 

[CBFalconer]

Joe Wright said:
.... snip ...

Nobody here drives on the wrong side of the road, except when
overtaking or when risking the wrath of the law (and society at
large) by driving home from spending a tenner in the pub...


Well, if you're asking why we drive on the proper - i.e. the
left - side of the road, the answer is simple: if the driver of
the oncoming vehicle attacks you, you want him on your right,
because that's the side on which your sword will be most
effective (if, like most people, you're right-handed). You can
use the other hand to control the horses.

I think that story is flawed. In the envisioned scenario, you
could get better sword action by keeping right. However, for
couched lances, keeping left makes more sense. Check it out with
Galahad, Lancelot, Bedevere, etc.

--
<http://www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.txt>
<http://www.securityfocus.com/columnists/423>

"A man who is right every time is not likely to do very much."
-- Francis Crick, co-discover of DNA
"There is nothing more amazing than stupidity in action."
-- Thomas Matthews

 

[Richard Heathfield]

CBFalconer said:

I think that story is flawed. In the envisioned scenario, you
could get better sword action by keeping right.

I disagree, and suggest that we test the matter by pitting the two
techniques against each other. We'll start our stagecoaches at opposite
ends of the lane, draw swords, and - on the word of command - set off
towards each other, with my vehicle firmly on the left side of the road
and yours firmly on the right. Last one standing buys the drinks.

However, for
couched lances, keeping left makes more sense. Check it out with
Galahad, Lancelot, Bedevere, etc.

I don't think they ever drove vehicles for a living.

 

[Richard Bos]

Richard Heathfield wrote:
And depending on when you started, this could be 240 to 1.

On my first trip to England, about 40 years ago now, a pint of bitter
cost one and six. A tot of gin with tonic was two shillings. Those were
the days.

Twelve pence to the shilling, twenty shillings to the Pound. As I recall
a Pound cost about five Dollars US. Those were the days.

I haven't been back to the UK for thirty years now. What does a pint of
bitter cost today?

Depends. Do you want to pay ****'s Egg Tax or not?

Here in Washington, DC a drink (even beer) will average five to six
dollars today in nicer places. Two dollars is about as low as you can go.

I don't think you could easily get a pint under two pounds in the Great
Wen. You certainly can easily get one more expensive than that. They're
cheaper Oop North.

Do y'all still drive on the 'wrong' side of the road? Why is that?

Yes, because they're still all brigands.

Richard

 

[Mark McIntyre]

Joe Wright said:



A couple of quid (about four bucks, I think).

Crikey. You clearly don't live in London... :-(

Only after drinking lots of bitter...

--
Mark McIntyre

"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it."
--Brian Kernighan