News for hackers. Stuff that matters.
Re:Interviewing programmers: coding test example explained by mynameishere on Thursday June 03, 2010 @10:38AM (#1401419)
I think you exaggerate. If you actually look at advertisements for c/c++ developers, they tend to contain words to the effect, "Must have 4-5 years experience in high speed algorithmic trading", etc. But if you know any good-paying jobs that only require the skill level you suggest, point me in that direction. (I mean that--I can get away from my current huge and horrible codebase. Speaking of which, I remember being appalled by the consistently awful misspelling of virtually everything until someone pointed out that its DOS origins required 8 character limits on filenames. I suspect such charming beasts as atoi and strlen had similar constraints, if only for purposes of saving RAM on PDP 11s.)
Re:Interviewing programmers: coding test example explained by wmil on Thursday June 03, 2010 @03:45PM (#1402293)
In the original C implementation function names could be as long as you wanted, but the compiler only looked at the first six chars.
Re:Interviewing programmers: coding test example explained by metageek on Friday June 04, 2010 @02:14PM (#1405097)
I thought it was the linker that truncated. So functions called fredBlogs() and fredBlugs() would be fine as long as they were in the same compilation unit, and not called from any other compilation unit.
Re:Interviewing programmers: coding test example explained by JoachimSchipper on Thursday June 03, 2010 @05:57PM (#1402738)
It's worse than that, actually: the C89/C90 standard allows this behaviour. Yes, many programs would break if compiled with such a theoretically conforming compiler.