Ohh, that brings back (bad) memories.
In $CPAN/src/unsupported/4.036/perl-4.036.tar.gz, you'll find a file
named lib/chat2.pl, which contains:
unless (socket(S, 2, 1, 6)) {
# XXX hardwired $AF_SOCKET, $SOCK_STREAM, 'tcp'
# but who the heck would change these anyway? (:-)
Yes, these were the correct constants on BSD, but they were wrong
for SysV, which meant that every SysV user sent me bug reports
about why chat2 didn't work for them. {sigh}
Thankfully, that file was "retired" as of Perl5, being replaced by the Expect module.
| [reply] [Watch: Dir/Any] [d/l] |
Finally easily accessible as... http://chat2.pl! Yes, I bought the domain just for the joke!
-- Randal L. Schwartz, Perl hacker
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
| [reply] [Watch: Dir/Any] |
| [reply] [Watch: Dir/Any] |
Yeah, I do that. I use TODO instead of XXX as the comment flag, but it amounts to the same thing. I've also been known on many occasions, despite whatever shred of sanity I may possess, to hardcode filepaths (although, I usually at least put them in a lexical variable at the top of the file). The thing is, I know better. I know that most of my Perl code eventually ends up running on at least both *nix and Win32, but I continually leave myself this cleanup to do the first time I have to run any given program on the other system.
At least I've finally just about got myself
trained to use File::Spec::Functions::catfile instead
of hardcoding the directory separator.
| [reply] [Watch: Dir/Any] |