Re: anyway to determine # rows before fetch loop ends and withoutseperate count(*)
am 18.11.2005 21:17:00 von listmail
> which ultimately makes the
> 50 or
> 60 line script you sent originally about 10 lines or less. (IE by
> using
> the array of array setup instead of some convoluted matrix that is
> structured god know how.
>
> That means in six months when you (or heaven forbid me) have to
> maintain
> your code we don't have to figure what you were smoking to get
> what you
> were after and what you personally define as a matrix and how
> you'd
> structure and access the data in said matrix, etc etc
Whatever is fueling the need for you to blow things out of such
proportion? I suggest that you refrain from trying to insult my or any
other person's intelligence who come to this mailing list seeking
help. You know as well as I do that the original script that I sent
was executing a push inside a while fetch loop, which is just another
way to do it ---> big deal. Is that so complicated??? No. If things
run efficiently and correctly either way does it really matter? Did
you include the number of lines in selectall_arrayref() sub too? -- Who
cares?
My post came about because of a fundamental misunderstanding of what is
actually going on. The communication of what I believed to be true
does not change what is actually happening, although it seems to do
that for you. Or is it that you spend to much time wanting to negate
someone's statements? I communicated things incorrectly and you sit
here and speculate these things and make these comments and honestly I
am only left to wonder who really finds you as beneficial as you think
that you are. I know ~I'm~ still learning. I go back and rewrite my
subs all the time as my knowledge progresses.
I'm not really sure who'd want you to maintain their code, but rest
assured you wont ever have to worry about maintaining mine.
Re: anyway to determine # rows before fetch loop ends and withoutseperate count(*)
am 18.11.2005 22:40:45 von mlists
listmail@triad.rr.com wrote:
>>which ultimately makes the
>>50 or
>>60 line script you sent originally about 10 lines or less. (IE by
>>using
>>the array of array setup instead of some convoluted matrix that is
>>structured god know how.
>>
>>That means in six months when you (or heaven forbid me) have to
>>maintain
>>your code we don't have to figure what you were smoking to get
>>what you
>>were after and what you personally define as a matrix and how
>>you'd
>>structure and access the data in said matrix, etc etc
>
>
> Whatever is fueling the need for you to blow things out of such
> proportion? I suggest that you refrain from trying to insult my or any
> other person's intelligence who come to this mailing list seeking
I meant no offense, only that calling an array reference an array
reference immediately is easier to work with than trying to understand
how this instance is applying some obscure idea of a matrix, thats all :)
> help. You know as well as I do that the original script that I sent
> was executing a push inside a while fetch loop, which is just another
> way to do it ---> big deal. Is that so complicated??? No. If things
but confusing to others and probably yourself in six months.
> run efficiently and correctly either way does it really matter? Did
> you include the number of lines in selectall_arrayref() sub too? -- Who
> cares?
ok, now *you're* getting insulting, I'm very sorry I spent my own time
trying to help you become a better programmer. I'm sorry if my trying to
keep it detailed and light was taken as an insult.
> My post came about because of a fundamental misunderstanding of what is
> actually going on. The communication of what I believed to be true
> does not change what is actually happening, although it seems to do
> that for you. Or is it that you spend to much time wanting to negate
> someone's statements? I communicated things incorrectly and you sit
> here and speculate these things and make these comments and honestly I
> am only left to wonder who really finds you as beneficial as you think
ok, so in what way is writing clearer, cleaner, more efficient code not
beneficial?
and why are you so mad about some inferred insult based on your ego
being hurt when you are doing it yourself blantenly and much worse?
> that you are. I know ~I'm~ still learning. I go back and rewrite my
> subs all the time as my knowledge progresses.
>
> I'm not really sure who'd want you to maintain their code, but rest
If you only knew..., this address is a sort of anonymous pseudonym for
me that the jupiterhost folks let me use, hehe :)
Again you missed the point: code will be maintained, by you or someone
else, so make it easier to do that by writing good code initially.
> assured you wont ever have to worry about maintaining mine.
Wow, now that was an insult not even slightly hidden in banter and had
no practical lesson attached...
The point I was trying to help you see is this:
If you are learning, learn the right practices early and you will save
yourself much headache in the future (IE understanding your old code,
rewriting code you know see as bad *and* relearning good practices). You
won't understand that now but you will later on down the road.
So to sum up, do whatever you want, don't take anyone's sage advise, I
just wish I could get my time back from trying to help you gain good
practices from the start.
I'll reply no further to pointless insults from you at this point, I
tried to help and wish I hadn't now.
Sorry you're overly sensitive, hopefully you'll be able work that out
with your therapist and medication and see the valuable lessons that I
attempted pass on.
good day
--
To unsubscribe, e-mail: beginners-unsubscribe@perl.org
For additional commands, e-mail: beginners-help@perl.org