comment on

"...He did ask for a learning exercise..."

Yes, but i didn't reply to the OP.

"...break the composite fields down..."

Yes, sure. Perhaps like this:

karls-mac-mini:monks karl$ perl -E ' say split /[\[\]]/, qq([22/Apr/20
+15:13:35:04 +1000])' 
22/Apr/2015:13:35:04 +1000

karls-mac-mini:monks karl$ perl -E ' say split /"/, qq("GET /bin/admin
+.pl HTTP/1.1")' 
GET /bin/admin.pl HTTP/1.1

karls-mac-mini:monks karl$ perl -E 'say join "\t", split /\s/, qq(GET 
+/bin/admin.pl HTTP/1.1)'
GET    /bin/admin.pl    HTTP/1.1
# usw...
[download]

I just wanted to show wrog that a solution that only uses split is possible.

Another question is ~~this it is desirable~~ if this is desirable. I guess some may call it abuse.

Edit: Better wording.

Best regards, Karl

ŤThe Crux of the Biscuit is the Apostropheť

In reply to Re^4: Question about the most efficient way to read Apache log files without All-In-One Modules from CPAN (personal learning exercise) by karlgoethebier
in thread Question about the most efficient way to read Apache log files without All-In-One Modules from CPAN (personal learning exercise) by lulz

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Keep It Simple, Stupid
	PerlMonks