On May 29, 6:06 am, [EMAIL PROTECTED] (Paul Lalli) wrote: > On May 29, 4:58 am, [EMAIL PROTECTED] (Brian) wrote: > > > On May 28, 6:14 pm, [EMAIL PROTECTED] (Paul Lalli) wrote: > > > > > oh yes, more important than all that minutiae... the push did not > > > > work for me in the working code. > > > > The push worked absolutely fine. It just didn't do what you wanted it > > > to. Learning how to parse your problem should be your first step > > > toward becoming a better programmer. > > > hmmm, misunderstanding there. The push worked fine in the sample I > > posted, but not in the more complex working program I had simplified > > as an example. > > nope, sorry, you're wrong. push() works perfectly well. It adds > elements to an array. If your program produced incorrect results, it > is because you did something wrong, not because "push didn't work."
ugh. pedantic semantics... > Of > course, as you haven't shown any code that produces these undesired > results, we can only guess as to what your actual problem was. yes, the real code is beyond what I would think of as "beginner" I truly meant to just post a small, working piece pf code that worked with some basic data structures... The DBI client is a bit more complicated, yes? > > > > > The array was being rewritten. > > > Then you didn't delcare your variables in the correct scope. > > understandable misperception on your part, as above > > Nope. If your array is being used in a loop, the contents of that > array are changing when you don't want them to be changing, and > instead want to be creating new arrays, you declared your array in the > wrong scope. > The sample I put out and the code I was working on are not identical. I declared my array in a different scope in the sample. Neither is "wrong", they are different. > > > > I had to use an array copy > > > > > push @tRespsA, [ @r1 ]; ## copy contents to an anonymous array, > > > > push array ref > > > > Do you understand *why* that was necessary? Do you understand the > > > difference between these two pieces of code? > > > actually, I do indeed. In C++, the concept of a deep copy, vs > > shallow copy vs ref > > comes up all the time. I am just learning the syntax here, not > > programming itself > > perhaps you should be. . . ugh. insults. I am not trying to insulting you Paul, why resort to that? You have no idea how many programs I've written, well. I'd say its bad form to assume the worst or lowest in people. > > > aha, a force to be reckoned with. Your point above about the docs is > > quite true. > > I dont have time to rewrite docs right now.. They do need work though > > You don't even have time to point out what you find to be "wrong" with > them? But instead you do have time to create examples that you claim > to be in the service of newbies, all the while saying that the docs > are bad? I'd suggest you could do with attending a few more time- > management seminars. > please examine logic - rewriting core Perl docs vs a 10 line sample program > > This is sometimes appearing to be contentious > > No sometimes about it. Every post you've made thus far is > contentious, and so I have answered in kind. > no, I'd suggest you read it that way.. Its notoriously difficult to convey context and nuance in a few lines of ascii text. Please refer to your RTFM and then essentially yelling at me for a modest sample program. I am not backing down from your brow-beating. I posted a small working sample program then found out more about the context I was dealing with and attempted to discuss it in an unassuming manner. For this I get these responses. phooey! I'll be posting again from time to time, and probably going to OSCon. Happy to talk with you anytime. May not respond every time though. I think I am sensing a pattern here... best regards -Brian -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/
