Ok, so I was looking to integrate some perl scripts into my IRC client, which happens to be EPIC, version 4, as EPIC5 seems to be trying to be the Perl6 of the text-mode IRC clients, and I'm not quite there yet (irssi, meanwhile is the Ruby of text-mode IRC clients). So I was looking for the correct syntax for the perlcall(6) function, (as opposed to the perl(6) and perlxcall(6) functions), and I get this from /HELP 6 perlcall:
Now, ironically, I will need the perl*call documentation to write a reader of the Wiki documentation so I can use it in EPIC (maybe). Lovely. More on that later.
*** Help on perlcalland that was it. Looking at /usr/local/share/epic/6_Functions/ for perlcall I see it is 0 bytes long. And so I look and there are 81 files like that. Shurely Shome mishtake right? Apparently not, asking in #epic I get informed that I should use the wiki, because 'it makes it a lot easier for us to give you correct/updated information'. Pathetic, really. Why can't the documentation be in source control and shipped with the source code? The online help pages that they have (which aren't categorized, its just a flat dump) could be generated from the text files instead. But oh no, we need a Wiki for documentation, and must have an internet connection just to read documentation, ugh. EPIC devs use Unix, right, they aren't hacking the source on their iPhones or Palms. right?
Now, ironically, I will need the perl*call documentation to write a reader of the Wiki documentation so I can use it in EPIC (maybe). Lovely. More on that later.
Leave a comment