Re: Oh ye who are in the gall or perlness...what maketh me mistaketh :)

I don't know...maybe I didn't get enough sleep last night. the "ne" vs "eq" worked.

The use of my "s is habit from shell scripting. Am I really to believe that Perl will not get things confused if I don't use "s for somethings? If so, great!! If not, what should I watch out for? When should I absolutely use "s in my scripts (besides the obvious prints, etc)? As I recall, I tried calling a function that I had written and I tried passing a value to the function without using quotes. When I tried to compile it Perl screamed at me because the value was not quoted. Once I quoted it all was well.

Sorry to have caused a burden guys. This really was, after looking at your responses, a dumb question. Thanks for the help.

----------
- Jim

Comment on Re: Oh ye who are in the gall or perlness...what maketh me mistaketh :)

Replies are listed 'Best First'.
Re: Re: Oh ye who are in the gall or perlness...what maketh me mistaketh :) by merlyn (Sage) on Apr 19, 2001 at 02:57 UTC
In Perl, quotes are for literals only. If you don't have a literal, you don't need a quote. In the shell, you have to use quotes to get many characters with embedded whitespace treated as a single entity. Different purpose, so different timing. -- Randal L. Schwartz, Perl hacker	[reply]
Re: Re: Re: Oh ye who are in the gall or perlness...what maketh me mistaketh :) by snafu (Chaplain) on Apr 19, 2001 at 19:37 UTC
Execellent. Thanks guys! ---------- - Jim	[reply]
Re: Re: Oh ye who are in the gall or perlness...what maketh me mistaketh :) by satchboost (Scribe) on Apr 19, 2001 at 02:54 UTC
If you pass a value, you need to quote it. If you pass a scalar ($foo), then you do not need to quote it. You're passing variables around, not values.	[reply]