Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • What? No IO::Socket?!?
    • Hey, that's taking the easy way out. IO::Socket is just a convenience wrapper around the raw socket routines.

      perldoc -f socket
      --
      J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
      • So whats wrong with opening /dev/tcp and using some judicious ioctl on it then ;-}

        /J\
        • by pne (661) on 2002.01.10 6:46 (#2987) Homepage Journal

          /dev/tcp! The luxury! Why, in my day, we had to compose Ethernet frames by hand and fiddle with network card I/O ports to get anything sent. And there weren't none of this full duplex nonsense back then, either. You young whippersnappers....

          --

          -- 
          Esli epei eto cumprenan, shris soa Sfaha.
          Aettot ibrec epesecoth, spakhea scrifeteis.

          • Re:Way to easy (Score:2, Interesting)

            I once wrote code to transmit 16 data streams in parallel using a parallel IO port which had each of the 16 bits connected to a different channel. The parallel port had to be written at the right times to generate the start and end of each bit. The bit stream for each port had to be modified to ensure that there were never more than 4 consecutive bits the same. Clock times for the processor were measured in Khz.

            This code was used to send updates to traffic light controllers. I don't know if they are s
          • Don't laugh. I worked at CERN on the safety systems for one on the large experiments. Local monitoring of the devices were done with small, VME and M68k based processor cards that they had stripped from some ancient, earlier experiment. These things should be in a museum.

            The good news was that they had a built-in Ethernet chip. The bad news was that they did not have enough RAM to load the TCP/IP drivers. Rather then install more RAM, the obvious (!) solution was for the safety system to just drive th