On Wednesday 31 January 2001 16:03, Dave Storrs wrote:
> "I'm sorry for writing you such a long letter; I didn't have time
> to write a shorter one."
> -- Abraham Lincoln
I thought that was a quote by Pascal?
--
Matthew Cline| Suppose you were an idiot. And
On Wed, Jan 31, 2001 at 06:37:21PM -0800, Matthew Cline wrote:
> On Wednesday 31 January 2001 16:03, Dave Storrs wrote:
>
> > "I'm sorry for writing you such a long letter; I didn't have time
> > to write a shorter one."
> > -- Abraham Lincoln
>
> I thought that was a quo
On Wed, Jan 31, 2001 at 05:55:13PM +, Simon Cozens wrote:
>Never over-design. Never think "Hmm, maybe somebody would find this
>useful". Start from what you know people _have_ to have, and try to
>make that set smaller. When you can make it no smaller, you've reached
>one point
From: Simon Cozens [mailto:[EMAIL PROTECTED]]
>
> Never over-design. Never think "Hmm, maybe somebody would find this
> useful". Start from what you know people _have_ to have, and try to
> make that set smaller. When you can make it no smaller, you've
> reached one point. That's a good point
I like Linus' quote, but that spirit would probably push Perl too
far into the computer scientists' language traps. Here's a Frank
Lloyd Wright quote I think works a bit better:
Five lines where three are enough is stupidity.
Nine pounds where three are sufficient is stupidity.
But to elimi
On Wed, Jan 31, 2001 at 12:05:46PM -0600, Jarkko Hietaniemi wrote:
> I've always shaken my head in disbelief when people measure/brag
> about programming prowess by the number of lines of code written.
> A true programmer is able to delete lines and still achieve the same
> functionality while sim
On Wed, Jan 31, 2001 at 05:55:13PM +, Simon Cozens wrote:
>Never over-design. Never think "Hmm, maybe somebody would find this
>useful". Start from what you know people _have_ to have, and try to
>make that set smaller. When you can make it no smaller, you've reached
>one point
Never over-design. Never think "Hmm, maybe somebody would find this
useful". Start from what you know people _have_ to have, and try to
make that set smaller. When you can make it no smaller, you've reached
one point. That's a good point to start from - use that for some real
implem
Matthew Cline wrote:
> Should there be method to tell an SV to change the internal representation
of
> the data? For example, if an SV was created as a string, but is being
turned
> into a float over and over again for use in equations, it would save
> processing time to convert the internal repr