Originally, Parrot was a HoaxLanguage
, referred to in a 2001 AprilFools
day announcement that PythonLanguage
were going to be merged, under the new name "Parrot" (http://www.perl.com/pub/2001/04/01/parrot.htm
However, it's since been adopted as the name for the PerlSix VirtualMachine
, which, ironically enough, is slated to support PythonLanguage
(among many others--see http://mail.python.org/pipermail/python-dev/2001-July/016406.html
). Or see ParrotCode
As one WikiZen
commented, "In a world with InterCal
everything is possible."
Take a look at the BefungeLanguage. :-)
Look at this code sample:
# copy stdin to stdout, except for lines starting with #
if dollar_underscore =eq= "#":
explains all the effort that went into this joke and is a fun to read. O'Reilly even announced a book about parrot and there was a nice interview with Larry Wall and Guido van Rossum.
And in a nod to the Monty Python origins of the Parrot name, this was written (after the AprilFools joke but before Parrot became the VirtualMachine project):
Is there more code? A formal spec? While the above code looks promising,
it is not enough to deduce a complete language spec from.
You saw the note about 'AprilFools day joke' above? No, there is no spec and probably there won't be more code or a spec in the future.
But I want to write an interpreter for it, in the gool ol' InterCal
tradition. But of course I want to be sure to implement true blue
Parrot, not some deviant offspring. -- StephanHouben
So I guess this is really a Dead Parrot Language? Or is it just resting?
How could something be dead or resting if it never has been alive?
The parrot is not dead, it's pining for the fjords.