[26671] in Perl-Users-Digest

home help back first fref pref prev next nref lref last post

Perl-Users Digest, Issue: 8778 Volume: 10

daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Dec 20 00:05:23 2005

Date: Mon, 19 Dec 2005 21:05:06 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)

Perl-Users Digest           Mon, 19 Dec 2005     Volume: 10 Number: 8778

Today's topics:
    Re: FAQ 5.34 Why can't I use "C:\temp\foo" in DOS paths <t18_pilot@hotmail.com>
        quotes (Raghuramaiah Gompa)
    Re: quotes <sbryce@scottbryce.com>
    Re: Socket operation crashes under HPUX&Solaris, but OK <kalala@hotmail.com>
        Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)

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

Date: Tue, 20 Dec 2005 01:57:52 GMT
From: "William Hymen" <t18_pilot@hotmail.com>
Subject: Re: FAQ 5.34 Why can't I use "C:\temp\foo" in DOS paths?  Why doesn't `C:\temp\foo.exe` work?
Message-Id: <AyJpf.7177$3Z.4145@newsread1.news.atl.earthlink.net>


>     Since all DOS and Windows versions since something like MS-DOS 2.0 or
so
>     have treated "/" and "\" the same in a path, you might as well use the
>     one that doesn't clash with Perl--or the POSIX shell, ANSI C and C++,
The forward slashes work for DOS executables only.
A useage like this:  ls c:/temp/text.txt  will fail.
-Bill


"PerlFAQ Server" <comdog@pair.com> wrote in message
news:do5eu5$idu$1@reader1.panix.com...
> This message is one of several periodic postings to comp.lang.perl.misc
> intended to make it easier for perl programmers to find answers to
> common questions. The core of this message represents an excerpt
> from the documentation provided with Perl.
>
> --------------------------------------------------------------------
>
> 5.34: Why can't I use "C:\temp\foo" in DOS paths?  Why doesn't
`C:\temp\foo.exe` work?
>
>
>     Whoops! You just put a tab and a formfeed into that filename! Remember
>     that within double quoted strings ("like\this"), the backslash is an
>     escape character. The full list of these is in "Quote and Quote-like
>     Operators" in perlop. Unsurprisingly, you don't have a file called
>     "c:(tab)emp(formfeed)oo" or "c:(tab)emp(formfeed)oo.exe" on your
legacy
>     DOS filesystem.
>
>     Either single-quote your strings, or (preferably) use forward slashes.
>     Since all DOS and Windows versions since something like MS-DOS 2.0 or
so
>     have treated "/" and "\" the same in a path, you might as well use the
>     one that doesn't clash with Perl--or the POSIX shell, ANSI C and C++,
>     awk, Tcl, Java, or Python, just to mention a few. POSIX paths are more
>     portable, too.
>
>
>
> --------------------------------------------------------------------
>
> Documents such as this have been called "Answers to Frequently
> Asked Questions" or FAQ for short.  They represent an important
> part of the Usenet tradition.  They serve to reduce the volume of
> redundant traffic on a news group by providing quality answers to
> questions that keep coming up.
>
> If you are some how irritated by seeing these postings you are free
> to ignore them or add the sender to your killfile.  If you find
> errors or other problems with these postings please send corrections
> or comments to the posting email address or to the maintainers as
> directed in the perlfaq manual page.
>
> Note that the FAQ text posted by this server may have been modified
> from that distributed in the stable Perl release.  It may have been
> edited to reflect the additions, changes and corrections provided
> by respondents, reviewers, and critics to previous postings of
> these FAQ. Complete text of these FAQ are available on request.
>
> The perlfaq manual page contains the following copyright notice.
>
>   AUTHOR AND COPYRIGHT
>
>     Copyright (c) 1997-2002 Tom Christiansen and Nathan
>     Torkington, and other contributors as noted. All rights
>     reserved.
>
> This posting is provided in the hope that it will be useful but
> does not represent a commitment or contract of any kind on the part
> of the contributers, authors or their agents.




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

Date: Tue, 20 Dec 2005 00:41:24 +0000 (UTC)
From: rgompa@steel.ucs.indiana.edu (Raghuramaiah Gompa)
Subject: quotes
Message-Id: <do7jvk$1ki$1@rainier.uits.indiana.edu>

I am "trying" to write a perl code to generate a file
with everybody's 'help'.

The output should be:

I am \myquote{trying} to write a perl code to generate a 
file with everybody{\justquote}s \singlequote{help}.

I know I can handle double quotes, but I am puzzled about 
single quote as you can see they may occur two different 
ways.

Please help. .. Raghu


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

Date: Mon, 19 Dec 2005 20:10:49 -0700
From: Scott Bryce <sbryce@scottbryce.com>
Subject: Re: quotes
Message-Id: <ofCdnasnXd2C6zreRVn-jw@comcast.com>

Raghuramaiah Gompa wrote:
> I am "trying" to write a perl code to generate a file
> with everybody's 'help'.
> 
> The output should be:
> 
> I am \myquote{trying} to write a perl code to generate a 
> file with everybody{\justquote}s \singlequote{help}.

use strict;
use warnings;

print qq(I am "trying" to write a perl code to generate a file with 
everybody's 'help'.);




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

Date: Tue, 20 Dec 2005 10:03:43 +0800
From: kalala <kalala@hotmail.com>
Subject: Re: Socket operation crashes under HPUX&Solaris, but OK under Windows
Message-Id: <43A7667F.C9049BE5@hotmail.com>

    Yeah, it works.
    Really thank you!

Jim Gibson дµÀ:

> In article <43A665AA.F0EE192B@hotmail.com>, kalala <kalala@hotmail.com>
> wrote:
>
> > Socket operation crashes under HPUX&Solaris, but OK under Windows
> >
> >     I am a perl newbie. Here's a problem annoying me!
> >     I am writing a TCP server(under Solaris). Everything seems OK: I can
> > telnet to it, and can see
> > the text sent by the server;But if I quit the telnet window, the TCP
> > server will crash silently,
> > without any prompt. I tested it under HPUX & Windows2000 to find the
> > reason, and find it worked under
> > windows2000, but still failed under HPUX.
> >     I put codes below:
>
> [snipped]
>
> You may need to handle or ignore the SIGPIPE signal in your server.
>
>  Posted Via Usenet.com Premium Usenet Newsgroup Services
> ----------------------------------------------------------
>     ** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
> ----------------------------------------------------------
>                 http://www.usenet.com



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

Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin) 
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>


Administrivia:

#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc.  For subscription or unsubscription requests, send
#the single line:
#
#	subscribe perl-users
#or:
#	unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.  

NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice. 

To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.

#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.

#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.


------------------------------
End of Perl-Users Digest V10 Issue 8778
***************************************


home help back first fref pref prev next nref lref last post