(Guildenstern) RE: Where oh where should I initialize my vars?

Okay. I didn't want to do it, since that means 65535 lines of data to look through to verify that all of my tabs were in the right place. However, if I would have paid more attention to the error, I would have seen that it happens on line 1 of __DATA__. Sure enough, line 1 had spaces instead of a tab. Fixed the tab, lost the error.
/me will be wearing a big "Idiot" sticker on my forehead the rest of the day. *sigh*

Guildenstern
Negaterd character class uber alles!

Comment on (Guildenstern) RE: Where oh where should I initialize my vars?

Replies are listed 'Best First'.
RE: (Guildenstern) RE: Where oh where should I initialize my vars? by Albannach (Monsignor) on Oct 26, 2000 at 00:22 UTC
This sort of thing happens to me quite often, but my choice would be to change your split() to be more flexible (i.e. split on tabs or spaces in this case) if possible, rather than edit your data, unless of course you won't ever need to run this on unknown data in the future. I figure if there is one line of bad data, there's bound to be more sometime (especially since my data have come from manual entry or rather crusty/rusty machinery). Just a thought.	[reply]

Replies are listed 'Best First'.

RE: (Guildenstern) RE: Where oh where should I initialize my vars?
by Albannach (Monsignor) on Oct 26, 2000 at 00:22 UTC

This sort of thing happens to me quite often, but my choice would be to change your split() to be more flexible (i.e. split on tabs or spaces in this case) if possible, rather than edit your data, unless of course you won't ever need to run this on unknown data in the future. I figure if there is one line of bad data, there's bound to be more sometime (especially since my data have come from manual entry or rather crusty/rusty machinery). Just a thought.

[reply]