<snip> > > > I am really sorry if I am appearing offensive , > I never meant to be .
Nope just curious I take it... > In perlsyn documen it does says " Don't do that " else it will get " > confused" > & quite below it says a C programmer does this - while same can be written > in perl as this > ( a shorter way ) - Now the "FACT" - you wana remove / delete the element - > go the "C" way > else learn foreach for shorter way - so learn both . > - but it seem to be a deficiency on it's part > that every such thing , which you expect as a "common sense" gets explained > as a mistake in > documentation - does it means only after reading the documentation line by > line you should start programmimg. > Or it happens , (what happens with me) you write a whole program using > foreach , > & after a lot of search , come to know "don't do that " & now replace that > with while or for loops > like in "C". > is it true that more flexibility in a language => more confused the > language will get > Yes and no. While I am not much of a low level programmer, the assumption you are making about the compiler always handling things in the same way is where the logic falls through. As I understand it, one compiler can and will act differently on the same language than another compiler, *especially* when on different OS's particularly where the underlying (read: chip architecture) is different, but most likely only in the cases like you mention, where it says the behaviour is undefined. Perl depends on these differences to some extent as a high level language and is therefore victim to them. For most tasks the logic is going to hold, but there is still a human element to all of this, decisions have been made for one reason or another and finding a 100% logical system is I would guess nearly impossible. Learning is 50% about failing, just because you might fail at something is not a good reason not to try it... http://danconia.org -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
