>I want to get a consensus here. Do you think one liners are faster than
>more extensive programs. Discuss.
Optimized for what? Speed? Space? Future maintenance?
In general, if it's code someone is going to have to maintain,
clarity is more important than character count. (It's also gener
On Dec 19, Ryan Guy said:
>kept doing that for a whole program.) Anyways what I am getting at is that
>the compiler optimizer works in tune with good coding practicing. It trips
>and falls when you try to cram all that shit on one-line (with a few
>exceptions). I always hear all this hype abou
Actually there Sparky, your intuition has failed you again. Taken into
consideration the amount of time wasted on brainstorming and the bad coding
practices put into play in one liners and (if we are thinking here. Think.
Think.) the way a program can be condensed into a series of one liners
(af
--- Ryan Guy <[EMAIL PROTECTED]> wrote:
> I want to get a consensus here. Do you think one liners are faster than
> more extensive programs. Discuss.
What, precisely, is there to discuss? Faster to execute? Faster to get work done?
Faster to
waste time with? One-liners are often used for a
Wednesday, December 19, 2001, 4:38:03 PM, Ryan Guy wrote:
> I want to get a consensus here. Do you think one liners are faster than
> more extensive programs. Discuss.
they're both perl
they're both using the same interpreter
they're both doing the same job
if they're executing the same code,
If you take into account the amount of time you save in
coding, one-liners are mostly faster.
You can also add to that the time saved on future maintenance.
Stef
Thus spake Ryan Guy on 19-Dec-2001 :
-> I want to get a consensus here. Do you think one liners are faster than
-> more extensive p
