Hey Curtis, > Your "Incorrect" statement is puzzling. Sure, that code is incorrect, but it's not what I posted.
Yes, you are correct, the two examples that I gave were not what you posted. That is why I posted yours above mine with the indents. You asked me for an example. I was giving you one. I already stated in a previous email to the list that I stood corrected. > If you're going to quote me out of context, allow me to point out two things: Again, see above. I have a habit of using long hash names for ease of reading, and have had strict bite me in the butt because of it. Since I use long hash keys a lot, I have gotten into the practice of always quoting my keys and values. So, I made a mistake in my statement. Again, I stand corrected on the hash key needing to be quoted. > > Shawn, I mean no offense by any of this. These could merely be matters of programming style, but > the => operator was specifically set up to allow this sort of functionality. My hash is very > clean and easy to read. If you prefer a different style, *shrug*. I am sorry if offended you. I was not saying your script was incorrect, mine was. I was showing where I got the 'You have to quote hash keys when using strict'. Shawn -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
