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

use Perl Log In

Log In

[ Create a new account ]

tinman (2063)

tinman
  (email not shown publicly)

tinman spent a few years mucking around industry before going back to school for a Masters. Currently not enjoying the weather in North England..

He wrote Perl that looked suspiciously like C code in 1998, while working as an intern, and has been trying to cure that bad habit ever since.

Journal of tinman (2063)

Saturday March 20, 2004
07:13 PM

industrial strength ByteArrays

[ #17985 ]

For a while, I wondered why some Commons projects existed. Reinventing the Logging and Output wheels, in particular, seemed like a useless expenditure of effort. Today, I needed to solve a buffering problem for ByteArrays. Java Outputstreams use tiny buffers and I kept seeing weird gc activity. Subclass? Nope. Commons IO to the rescue. Now I know why it was written :)

While I'm on the subject of IO, it seems pretty pertinent to mention this gem . IO:All, written in what is about 100 ^W1000 (thanks to pjm for pointing out my "large values of 100", I meant to say 1000) lines of code basically gives you socket, directory, file and string handling, all in one module. I'm still trying to wrap my brain around his "inheritable exporting" technique. Spiffy, indeed.

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.