It is just the result of a long day and we had gotten a little giddy. For many, many years (ever since I'd been on the team), we'd always joked about replacing some error message in the compiler for one of the most common errors with a similar message. Internally we've always joked and poked fun at different things and people (mostly on the team itself). If you don't have a sense of humor, you're destined to an early grave.
It was a simple conversation;
"Oh, you should have raised the EProgrammerNotFound exception in that function."
"LOL! We should add that exception and see who notices."
"I wonder how much speculation there will be about why it is there?"
So, I guess all I can say is, "You've all played right into our hands ;-)... Buwahahaha! pwned!"
It is used in conjunction with the "fix-inline" technology which requires that the programmer has to be linked into the exe file ;-)
It was introduced in Delphi 2009, still present in Delphi 2010, and recently got some more attention on the internet.
I think it is an easter egg, similar to "EBCAK" (Error Between Chair and Keyboard), and the skipping of Delphi version number 13.
EProgrammerNotFound
I don't think EProgrammerNotFound is actually meant to be used at all, but since it is there, people will jokingly use it (similar like putting a stray "const False = True; True = not False;" in someone elses sourcecode).
--jeroen
The origin is debatable, but it's been known for a while...
Marco Cantu joked about it in a "Fun Side of Delphi" session.
IMO, it should be used more often ;-)
Read on:
http://wings-of-wind.com/2010/01/12/best-programming-feature-ever/
http://blog.barrkel.com/2008/11/reference-counted-pointers-revisited.html
PS: I don't think it exists in Delphi Prism, FreePascal or C# (but it should). <G>
It's the runtime analog of the compiler's "Syntax error: Programer expected." ;>
It is a kind of self describing joke, you can try this code
raise EProgrammerNotFound.Create('Jack is away');
or
raise ENotImplemented.Create('May be in future this will work');
The above works in Delphi 10 Seattle.
With programmer, it is not the programmer that is sitting behind Delphi that is referenced. I think it is used for the fact that in D2009 and above they planned (never used it don't know if it works) that every object was waitable.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With