Lit. Buffer overruns 1695
I respectfully disagree. I think that is an over-generalization. It has nothing to do with whether the customers are internal or external, or whether there...
Yes, the results are logrithmic, not linear... (I think I just messed up using English ASCII but you'll know what I'm talking about...you've been posting about this aspect for years.)
What I would you to speculate about is: If PLI had been distributed as freely and widely as C would the oodles of code still be "buffer safe"? I've only met PLI once and that was in the form of the cards I punched for the guy who wrote the code 37 years ago so I don't remember much. PLI never got popular because it was a PITA to use. In my area one had to drive from Kalamazoo to Ann Arbor, submit the card deck, and then drive back with the results because a user was only allowed one run-visit.
But would the evolution of the functionality of PLI match C? Would the bounds checking have given the coders enough of a headache during their development cycles that they would have defaulted to an "easier" technique?
My apologies if I'm not writing clearly enough.
PLI was guarded by formidable bit gods. C was not. C was not guarded because ATT's business was not primarily the computer biz. The messes we see in Unix are directly because of that...IMO.
BAH
Subtract a hundred and four for e-mail.
spit Perhaps. Don't knock unless you've tried it. :-) Internal politics makes development work a real headache. What tradeoffs you choose makes a huge difference. I wrote more about some in another post. Think about one...
Alt Folklore Computers from Newsgroups