Click here to get back home

FAQ 7.3 Do I always/never have to quote my strings or use semicolons and commas?
 Home | NewsGroups | Search | About
Login Password
Register Now!
 comp.lang.perl.misc    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content
Subject Author Date
FAQ 7.3 Do I always/never have to quote my strings or use semicolons and commas? PerlFAQ Server 03-19-2008
Posted by PerlFAQ Server on March 19, 2008, 3:03 pm
Please log in for more thread options
 This is an excerpt from the latest version perlfaq7.pod, which
comes with the standard Perl distribution. These postings aim to
reduce the number of repeated questions as well as allow the community
to review and update the answers. The latest version of the complete
perlfaq is at http://faq.perl.org .

--------------------------------------------------------------------

7.3: Do I always/never have to quote my strings or use semicolons and commas?

Normally, a bareword doesn't need to be quoted, but in most cases
probably should be (and must be under "use strict"). But a hash key
consisting of a simple word (that isn't the name of a defined
subroutine) and the left-hand operand to the "=>" operator both count as
though they were quoted:

This is like this
------------ ---------------
$foo $foo
bar => stuff 'bar' => stuff

The final semicolon in a block is optional, as is the final comma in a
list. Good style (see perlstyle) says to put them in except for
one-liners:

if ($whoops) { exit 1 }
@nums = (1, 2, 3);

if ($whoops) {
exit 1;
}

@lines = (
"There Beren came from mountains cold",
"And lost he wandered under leaves",
);



--------------------------------------------------------------------

The perlfaq-workers, a group of volunteers, maintain the perlfaq. They
are not necessarily experts in every domain where Perl might show up,
so please include as much information as possible and relevant in any
corrections. The perlfaq-workers also don't have access to every
operating system or platform, so please include relevant details for
corrections to examples that do not work on particular platforms.
Working code is greatly appreciated.

If you'd like to help maintain the perlfaq, see the details in
perlfaq.pod.

Posted by szr on March 21, 2008, 12:02 am
Please log in for more thread options
 PerlFAQ Server wrote:
> This is an excerpt from the latest version perlfaq7.pod, which
> comes with the standard Perl distribution. These postings aim to
> reduce the number of repeated questions as well as allow the community
> to review and update the answers. The latest version of the complete
> perlfaq is at http://faq.perl.org .
>
> --------------------------------------------------------------------
>
> 7.3: Do I always/never have to quote my strings or use semicolons and
> commas?
>
> Normally, a bareword doesn't need to be quoted, but in most cases
> probably should be (and must be under "use strict"). But a hash key
> consisting of a simple word (that isn't the name of a defined
> subroutine) and the left-hand operand to the "=>" operator both
> count as though they were quoted:
>
> This is like this
> ------------ ---------------
> $foo $foo
> bar => stuff 'bar' => stuff

Shouldn't this be:

bar => 'stuff' 'bar' => 'stuff'

?

Thanks again for the wonderful documentation you people have put a lot
of time into.

--
szr



Posted by brian d foy on March 21, 2008, 6:42 pm
Please log in for more thread options
wrote:




> > 7.3: Do I always/never have to quote my strings or use semicolons and
> > commas?


> > This is like this
> > ------------ ---------------
> > $foo $foo
> > bar => stuff 'bar' => stuff
>
> Shouldn't this be:
>
> bar => 'stuff' 'bar' => 'stuff'

It's not the literal string 'stuff', just a placeholder. It's just, um,
stuff.

Posted by szr on March 21, 2008, 7:28 pm
Please log in for more thread options
brian d foy wrote:
>
>
>
>
>>> 7.3: Do I always/never have to quote my strings or use semicolons
>>> and commas?
>
>
>>> This is like this
>>> ------------ ---------------
>>> $foo $foo
>>> bar => stuff 'bar' => stuff
>>
>> Shouldn't this be:
>>
>> bar => 'stuff' 'bar' => 'stuff'
>
> It's not the literal string 'stuff', just a placeholder. It's just,
> um, stuff.

I figured as much, though I don't think being that loose is a good idea
for an FAQ example snippet of code. I may understand what you meant, as
do you and many others, but I still think care should be taken in
situations like this where code could too easily be misread by those
it's meant to help :-)

--
szr



Similar ThreadsPosted
FAQ 7.3 Do I always/never have to quote my strings or use semicolons and commas? February 11, 2005, 12:03 am
FAQ 7.3 Do I always/never have to quote my strings or use semicolons and commas? April 28, 2005, 11:03 pm
FAQ 7.3 Do I always/never have to quote my strings or use semicolons and commas? July 14, 2005, 4:03 pm
FAQ 7.3 Do I always/never have to quote my strings or use semicolons and commas? October 15, 2005, 10:03 pm
FAQ 7.3 Do I always/never have to quote my strings or use semicolons and commas? November 22, 2005, 11:03 pm
FAQ 7.3 Do I always/never have to quote my strings or use semicolons and commas? January 29, 2006, 12:03 am
FAQ 7.3 Do I always/never have to quote my strings or use semicolons and commas? September 1, 2006, 3:03 pm
FAQ 7.3 Do I always/never have to quote my strings or use semicolons and commas? November 16, 2006, 9:03 am
FAQ 7.3 Do I always/never have to quote my strings or use semicolons and commas? March 13, 2007, 4:03 pm
FAQ 7.3 Do I always/never have to quote my strings or use semicolons and commas? May 29, 2007, 3:03 am

Our other projects:

Art Dolls, Fairies and Mermaids - Sunnyfaces.net

Roy's Linux, Programming and Search Engines messages

1-Script XML SitemapXML Sitemap