Re: Re: Pesky little URL files to HTML

This (your code that is) is too cool for snappy comebacks! But to make a feeble attempt, I can only ask: How do you put up with all of those annoying key words in your search for better otimization?—all right,all right I said it was feeble<g>

–hsm

"Never try to teach a pig to sing…it wastes your time and it annoys the pig."

Comment on Re: Re: Pesky little URL files to HTML

Replies are listed 'Best First'.
Re: Re: Re: Pesky little URL files to HTML by chromatic (Archbishop) on Dec 17, 2001 at 07:33 UTC
Does it help to say it comes with experience? Part of it is learning and becoming familiar with language features, and part of it is learning common programming patterns and technique. With Perl, you'll never unlock the full power of the language until you see lists and how to put them together. If you realize that you're just manipulating elements of a list, map jumps out at you. Since print takes a list, it's easy to do the right thing and to decouple the transformation (HTML-izing URIs) from the action of printing them. You don't usually see this all in one step, but if you do a couple of little transformations, you can open the door for bigger gains. They start to add up.	[reply]

Replies are listed 'Best First'.

Re: Re: Re: Pesky little URL files to HTML
by chromatic (Archbishop) on Dec 17, 2001 at 07:33 UTC

With Perl, you'll never unlock the full power of the language until you see lists and how to put them together. If you realize that you're just manipulating elements of a list, map jumps out at you. Since print takes a list, it's easy to do the right thing and to decouple the transformation (HTML-izing URIs) from the action of printing them.

You don't usually see this all in one step, but if you do a couple of little transformations, you can open the door for bigger gains. They start to add up.

[reply]