On Tue, Nov 28, 2000 at 11:16:57AM +0000, Nicholas Clark wrote: > > This is a bug report for perl from nick@talking.bollo.cx, > generated with the help of perlbug 1.33 running under perl v5.7.0. > > > ----------------------------------------------------------------- > [Please enter your report here] > > What's the <expletive> point of example code if it's buggy? > Not only do some of the perlipc code fail to compile in the first place, > but even when you fix those bugs two have subtle precedence bugs w.r.t. > "or" versus "||" and scalar/list context. > > Bugs remaining > > 1: I've no idea what the missing text after "We'll" should be: > > a time. Multithreaded servers are covered in Chapter 6 of > the Camel. > > Here's the code. We'll > > #!/usr/bin/perl -w > > > 2: The example that follows uses Net::hostent. It's not working becuse > Net::hostent in bleadperl is shagged. > > 3: Net::hostent doesn't have a regression test to detected that it's shagged. Writing a portable test that still tests anything useful for the gethost* is tough. Remember that the contents or the existence of the /etc/hosts file might be largely irrelevant to to results of the gethost* calls. -- $jhi++; # http://www.iki.fi/jhi/ # There is this special biologist word we use for 'stable'. # It is 'dead'. -- Jack CohenThread Previous | Thread Next