News for hackers. Stuff that matters.
Re:C Finally Gets A New Standard by warmwaffles on Tuesday April 10, 2012 @10:15AM (#3822234)
Back when C was first pioneer'd this was an issue. However this is the 21st century and yes we could have better full names but the standard from before is kept for consistency. I think deprecation and renaming of everything is out of the question at this point as companies and developers have invested considerable amounts of time in building applications using the good ole "fprintf" or "malloc".

I wonder what the ramifications would be if someone went through and properly named the functions.

Re:C Finally Gets A New Standard by scott_s on Tuesday April 10, 2012 @01:19PM (#3823289)
You mean back when C was first creat'd.
Re:C Finally Gets A New Standard by gruseom on Wednesday April 11, 2012 @12:39PM (#3828329)
I recently found myself reading Mason & Dixon and trying to figure out what the rule is for those apostrophes. Pynchon wrote that book in a hybrid of 18th and 20th century English (which is brilliant and possibly also annoying) and boy does he apostrophize. At first it seemed like all the past forms were apostrophiz'd but then I noticed many of them were elongated after all. It appears that the rule is to spell out the "e" in "ed" when it's articulated and use an apostrophe when it's unpronounc'd. I suppose this ought to have been obvious from first principles but I only hit on it by painstaking induction :)
Re:C Finally Gets A New Standard by scott_s on Wednesday April 11, 2012 @04:30PM (#3829497)
To be fair, it should be "created." I was making a joke based on the fact that the original function name to create a file in C was in fact called "creat". If I added the (pronounced) "e", then the joke would be lost!
Re:C Finally Gets A New Standard by gruseom on Wednesday April 11, 2012 @04:45PM (#3829555)
Ah, I missed that. Creatted? :)