[24196] in Perl-Users-Digest
Perl-Users Digest, Issue: 6388 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Mon Apr 12 11:06:13 2004
Date: Mon, 12 Apr 2004 08:05:09 -0700 (PDT)
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, 12 Apr 2004 Volume: 10 Number: 6388
Today's topics:
ANNOUNCE: UnixODBC 0.31 (Robert Kiesling)
Re: CPAN.pm can't find libs <spamtrap@dot-app.org>
Re: CPAN.pm can't find libs <jwillmore@remove.adelphia.net>
Re: format, stdout, with 'swrite' no hot ^ (woof)
Re: I cann't scale gif with correctly with perlmagick. (kenny)
Re: I cann't scale gif with correctly with perlmagick. <postmaster@castleamber.com>
Re: perldoc incompetence: perlre /s <tadmc@augustmail.com>
Re: perldoc incompetence: perlre /s <uri@stemsystems.com>
Re: perldoc incompetence: perlre /s <jwillmore@remove.adelphia.net>
Re: regex not matching high end (Anno Siegel)
Re: regex not matching high end <postmaster@castleamber.com>
Re: regex not matching high end <matternc@comcast.net>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Sat, 10 Apr 2004 23:45:02 GMT
From: rkies@cpan.org (Robert Kiesling)
Subject: ANNOUNCE: UnixODBC 0.31
Message-Id: <Hw22sJ.745@zorch.sf-bay.org>
Description
-----------
UnixODBC provides a toolkit for writing Perl ODBC clients. It
implements a functional interface for a subset of the API implemented
by unixODBC, http://www.unixodbc.org/, and an extended,
object-oriented API that ODBC connectivity for network hosts.
The package also includes library modules that manage DSN templates
and configure driver properties, and write RSS output from ODBC
queries.
The client programs in the package provide text-mode, Perl/Tk and
mod_cgi Web User Interfaces, as well as bridge services. The clients
can perform data management tasks on local and network hosts.
The README file, below, describes the libraries, client programs, and
system requirements.
Download
--------
You can download UnixODBC.pm from the following sites:
http://sourceforge.net/projects/unixodbc-pm/.
ftp://ftp.cpan.org/pub/CPAN/authors/id/R/RK/RKIES/.
UnixODBC.pm 0.31 README
-----------------------
UnixODBC.pm Installation
- Contents
- Overview
- Ins
talling UnixODBC.pm
- Testing UnixODBC.pm
- Installing and Configuring the Bridge Server
- Installing the GUI Data Manager, Tkdm
- Installing the Web data manager
- Text-mode Programs
- Troubleshooting
- Copyright
- Overview
UnixODBC.pm provides Perl programs with a subset of the X/Open
ODBC Application Programming Interface implemented by unixODBC
from http://www.easysoft.com/. UnixODBC.pm also provides an API
that implements ODBC function calls for TCP/IP network host
systems. Refer to the section, "Installing and Configuring the
Bridge Server," below.
The UnixODBC.pm Text-mode programs and Web and GUI data managers
can perform ODBC queries on local and networked systems. Refer
to the sections, Text-mode Programs," "Installing the GUI Data
Manager, Tkdm," and, "Installing the Web Data Manager," below,
and the file, "INSTALL," in the tkdm/ subdirectory.
- Installing UnixODBC.pm
The unixODBC libraries, from http://www.unixodbc.org/, and an
ODBC driver for your DBMS server, should be installed and
working before installing UnixODBC.pm. UnixODBC.pm has been
tested with unixODBC versions 2.2.0 - 2.2.6. UnixODBC.pm also
requires the unixODBC C-language include files from unixODBC.
They should have been installed in /usr/local/include when you
install unixODBC. If the header files aren't there, you can
find them in the include/ subdirectory of the unixODBC package.
The dbms/README describes DBMS and driver installation for
MySQL and PostgreSQL. It also describes how to handle
PostgreSQL exception signals that can cause Perl programs to
terminate.
UnixODBC.pm itself requires the following Perl libraries:
- Net-Daemon-0.35 - 0.37
- PlRPC-0.2015 - 0.2017
- Tk800.021 - 0.23
IMPORTANT - Each host must have identical versions of Perl,
Net::Daemon, PlRPC, and the modules they require.
Tkdm also requires Perl/Tk.
Versions of Perl prior to 5.6.0 might not provide Sys::Syslog.pm
and Storable.pm. In that case these modules must be installed also.
To build and install the modules, use the following commands:
$ cd UnixODBC-<version>
$ perl Makefile.PL
$ su
# make install
When initially installing UnixODBC.pm, the installation warns
that UnixODBC.pm is not installed. If the installation warns
that other library modules are not installed, you should install
them before proceeding.
To run the test script dbms/test.pl, you need to have
installed the data in the dbms subdirectory. Refer to,
"Testing UnixODBC.pm," below. The ODBC driver needs to be
configured for your DBMS and a data source using either
odbcinst or ODBCConfig.
Standard Disclaimer - UnixODBC.pm and the client and server
scripts were written with Perl installed in /usr/bin. If Perl
scripts print an error message like:
sh: ./client: no such file or directory
It means the script can't find the Perl interpreter. Either
change the path on the first line of the script to the location
of the perl binary (the output of, "which perl"), or create a
symlink /usr/bin/perl to the actual Perl program.
- Testing UnixODBC.pm
UnixODBC.pm is known to work with MySQL and PostgreSQL on Linux
and Solaris systems.
Running, "make test," makes sure that the library modules load
correctly.
The dbms/test.pl script excercises the unixODBC API more
thoroughly. For the script to complete, the DBMS must have
installed the test data in the dbms/ subdirectory, and you must
have configured a DSN for the test data. Refer to the file
dbms/README for notes about MySQL and PostgreSQL DBMS's.
Running test.pl is likely to result in at least a few errors.
The script is designed to test the subset of ODBC API functions
that UnixODBC.pm implements as exhaustively as possible, and as
many different ODBC DBMS drivers as possible (currently the MyODBC
and Easysoft PostgreSQL drivers).
- Installing and Configuring the Bridge Server
IMPORTANT (Again) - The versions of Perl, Net::Daemon, Storable,
and PlRPC on each host MUST be the identical. Net::Daemon,
in particular, checks for version information when authenticating,
and PlRPC generates protocol errors when communicating with
different
versions. Storable also relies having the same version of itself and
Perl on local and remote systems.
UnixODBC and the supporting libraries are not thread-safe (yet).
You may encounter thread exceptions on some systems with Perl
5.8.0 configured with ithreads.
Net::Daemon errors are commonly recorded in the syslog.
Although you can configure the log messages, check the syslog
first. Refer to, "Troubleshooting," below.
The bridge server runs as user nobody and uses port 9999. To
change the configuration, edit /usr/local/etc/odbcbridge.conf
after installation. The RPC::PlServer(3) man page describes the
settings Example server and client scripts are in the bridge/
subdirectory. For further examples of writing Perl RPC clients
and servers, refer to the man pages for RPC::PlServer and
RPC::PlClient, and the ProxyServer.pm module in the Perl DBI
bundle.
Install UnixODBC.pm as describe above. This step also installs
/usr/local/etc/odbclogins which is necessary for the Web data
manager. You can add host and login information as described below.
If the installation proceeded correctly, the core libraries and
bridge server daemon should be installed in the proper directories,
and you should be able to start and stop the daemon by typing:
# /usr/local/etc/init.d/unixodbc start
# /usr/local/etc/init.d/unixodbc stop
Manual Installation - Create the directories /usr/local/etc,
/usr/local/var, and /usr/local/sbin if they don't exist. Then,
$ su
# mkdir /usr/local/var/odbcbridge
# chown nobody /usr/local/var/odbcbridge
# cp bridge/odbcbridge.conf /usr/local/etc
# cp bridge/odbclogins /usr/local/etc
# chmod 0600 /usr/local/etc/odbclogins
# chown nobody /usr/local/etc/odbclogins
# mkdir /usr/local/etc/init.d
# cp bridge/unixodbc /usr/local/etc/init.d
# cp bridge/odbcbridge /usr/local/sbin
# chmod +x /usr/local/sbin/odbcbridge
If everything is installed correctly, you should be able
to start and stop the server by typing:
# /usr/local/etc/init.d/unixodbc start
# /usr/local/etc/init.d/unixodbc stop
To start the server when the system starts, install the unixodbc
script in the same directory as the other local startup scripts,
refer to the system administration documents for information
about how to start daemons during system initialization.
- Installing the GUI Data Manager, Tkdm
The GUI data manager tkdm is installed when UnixODBC.pm is
installed. Refer to the man page ("man tkdm") and the
tkdm/README file for configuration instructions.
- Installing the Web data manager
The Web data manager works with the Web servers: Apache 1.3 and
2.0, and the Web browsers: Mozilla 1.0, Netscape 4.75, and Internet
Explorer 3.03.
The document describes a configuration that uses
/usr/local/apache/htdocs as the Apache DocumentRoot directory and
/usr/local/apache/cgi-bin as the CGI script directory. Make the
necessary adjustments for the system's Apache configuration.
APACHE CONFIGURATION - Httpd.conf must be configured to load
mod_perl,
mod_env, and mod_ssi, and use server-side includes. On some systems,
LD_LIBRARY_PATH in the server's environment must be able to locate
all
of the libraries that the DBMS server, ODBC, and Perl require.
The data manager is configured to be installed in the,
"datamanager,"
subdirectory of, "htdocs," or the directory named in the httpd.conf
DocumentRoot directive. If installing in a different subdirectory,
modify the directives shown below for httpd.conf accordingly, and
change the value of $folder in the CGI script, datamanager.cgi.
If the Apache server does not have server-side includes enabled,
add the following lines to httpd.conf:
<Directory "/usr/local/apache/htdocs/datamanager">
Options FollowSymLinks Includes
</Directory>
AddType text/html .shtml
AddHandler server-parsed .shtml
To add the path for all of the libraries to the server's
environment, add a line like this to httpd.conf:
SetEnv LD_LIBRARY_PATH
/usr/lib:/usr/local/lib:/usr/local/mysql/lib/mysql
The specific names of the directories depend on the system's
Apache and DBMS server configuration.
Then restart the Apache:
# /usr/local/apache/bin/apachectl restart
Then install the files.
$ su
# mkdir /usr/local/apache/htdocs/datamanager
# cp datamanager/*.html /usr/local/apache/htdocs/datamanager
# cp datamanager/*.shtml /usr/local/apache/htdocs/datamanager
# cp datamanager/*.gif /usr/local/apache/icons
# cp datamanger/odbclogins /usr/local/etc
# cp datamanager/*.cgi /usr/local/apache/cgi-bin
# cd /usr/local/apache/cgi-bin
# chmod +x tables.cgi datamanager.cgi odbclogin.cgi
Edit the path to the perl interpreter on the
first line of tables,cgi, datamanager.cgi,
odbclogin.cgi to the path of the actual perl
interpreter. The path should be either
/usr/local/bin/perl, /usr/bin/perl, or the output
of the shell command, "which perl."
# cd /usr/local/etc
# chmod 0600 odbclogins
# chown nobody odbclogins # Use the UID/GID of httpd.conf's,
# chgrp nobody odbclogins # "User," and, "Group," directives.
Edit each line of the file /usr/local/etc/odbclogins for
the login of each system that has a bridge server installed.
The format of each line is:
host::user::password
The user names and passwords need not be the same as those
used to log in to the DSN's. They simply need to allow the
clients (either the CGI scripts or the command-line scripts)
to log in to the bridge server on the remote system. They
need to be actual users with passwords, with their own
entries in /etc/passwd.
IMPORTANT - /usr/local/etc/odbclogins contains login data
for remote systems. It is important to change the permissions
and ownership so that it can be read by the httpd server
processes ONLY (i.e., the CGI scripts). Apache servers often run
as user nobody, group nobody. The ownership of
/usr/local/etc/odbclogins should be the values of the User and
Group http.conf directives.
Also, do a, "chmod 0600 /usr/local/etc/odbclogins," to remove,
"group," and, "other," permissions from the file. If this isn't
secure enough, you can also create a separate UID (www, for
example) and make sure to change the User directive value in
httpd.conf.
Standard Disclaimer (Again) - The CGI scripts are written to
find Perl as /usr/bin/perl. If that isn't the location of the
Perl interpreter, then either edit the first line of the scripts
to reflect the actual location of the perl binary (the output of,
"which perl") or make /usr/bin/perl symlink to the interpreter.
The ODBC logo is modified from the XPM in the unixODBC-2.2.2
Data Manager source tree.
CGI script errors are recorded in the Apache error_log, even if
they don't appear in the browser window. If the scripts seem
to work right, but the data manager can't connect to data sources,
look for the bridge error messages in the syslog, and consult the
section, "Troubleshooting," below.
- Text-mode Programs
The eg/ subdirectory contains example ODBC clients for
locally hosted ODBC servers. The scripts that log into a
data source require the DSN, DBMS login name and DBMS
password as command line arguments. The client scripts in
the bridge/ subdirectory, for networked ODBC servers,
additionally require the name or IP address of the host
system.
Documentation for the client scripts are in the man pages.
The command line option, "--help," prints a brief help
message.
# alltypes --help
Clients for local host ODBC queries.
- alltypes List the SQL data types for a DSN.
- apifuncs ODBC API functions that a driver implements.
- colattributes Column attributes for a title.
- connectinfo Connection attributes.
- datasources DSN's on the local system.
- driverinfo Drivers on the local system.
- rssoutput Output result set as RSS RDF file.
- gutenberg.cgi CGI query with Project Gutenberg data in dbms/.
Clients for remote DSN queries are in the bridge/ subdirectory.
sampleclient and sampleclient2 - Testing ODBC function
calls using the peer to peer bridge.
- remotedsn List the DSN's of a remote system.
- remotetables List the tables of a remote DSN.
- Troubleshooting
- Perl error messages similar to,
<programname>: not found
indicate that the script cannot locate the Perl interpreter.
The programs have this automatically configured during
installation. The CGI scripts assume that the Perl binary
is /usr/bin/perl. If it isn't, you can make a symlink
from the actual Perl interpreter, or edit the first line in
the scripts to the path of the Perl binary.
- If a program seems to take forever to start, it generally
indicates that the bridge server can't make a connection
to another machine on a network, and usually indicates that
a network system is not accessible.
- "Failed to make first connection...," to a DSN generally
means that either the remote bridge server is not running,
the client was not able to log in, or the perl and library
versions are different on each system. Check the installation
and configuration of the bridge server (above and, "man
odbcbridge"), and make sure that you can connect to the remote
DSN with a text-mode client like remotedsn ("man remotedsn")
or remotetables ("man remotetables").
If the data manager can connect to local data sources but not
remote data sources, the problem is likely in the RPC network
layer. Ensure that the versions of Perl, Net::Daemon,
Storable, and RPC::PlServer are identical on local and remote
systems. Try connecting with one of the text mode clients
(remotedsn, remotetables) to help diagnose the problem.
The servers at all levels (DBMS server, HTTP server, bridge
server) perform caching on the local and remote machines. It
might be necessary to restart both systems, especially if you
change the configuration of one or more systems, or upgrade
the software. Remember to re-start the bridge server if you
change the system configuration.
- If you receive, "Unexpected EOF while waiting for server
reply," errors while logging into a DSN, try restarting the
bridge server from a terminal session.
- "Out of memory during large request," and "Maximum
message size exceeded," errors occur when the size of a
result set is greater than 64 kb. This is because the
bridge server uses integers as packet indexes. Try to
narrow the SQL query to produce a smaller result set.
- Error and/or status messages do not show up in the
system logs. The clients, especially the Web data manager,
can record activity by the UnixODBC bridge server, the ODBC
Driver Manager, and the HTTP server in up to three (that's
right, three) different system logs.
1. UnixODBC bridge servers and clients use the syslog,
"daemon," facility to record activity. If daemon logging is
not enabled (i.e., there is no, "daemon.log," file), typically
add a line like this to /etc/syslogd.conf, for example (on
Linux systems):
daemon.* /var/log/daemon.log
Refer to the man pages for syslogd, syslogd.conf, and/or
syslog.conf depending on the Unix version. If the 'debug' option
in /usr/local/etc/odbcbridge.conf is non-zero the ODBC server
generates additional status and error messages. Remember to
restart the syslog daemon after making configuration changes.
2. The functions dm_log_open(<logfilename>) and dm_log_close()
in UnixODBC.pm and UnixODBC::BridgeServer.pm begin and end the
logging of ODBC driver manager function calls.
3. The HTTP server records HTTP and CGI script errors in the
server's error_log.
- Authorship and Copyright
UnixODBC.pm is written by Robert Kiesling, rkies@cpan.org.
Copyright <A9> 2002-2004 by Robert Kiesling and licensed under
the same terms as Perl. Refer to the file, "Artistic," for the
details.
$Id: README,v 1.19 2004/03/14 00:27:44 kiesling Exp $
------------------------------
Date: Mon, 12 Apr 2004 09:08:03 -0400
From: Sherm Pendley <spamtrap@dot-app.org>
Subject: Re: CPAN.pm can't find libs
Message-Id: <xvadnQnLjd0zCefdRVn-gg@adelphia.com>
kj wrote:
> I'm trying to get CPAN.pm to install XML::LibXML for me. It aborts
> the installation with a message saying that it can't find libxml2,
> even though libxml2.so.2 is in /usr/lib.
A package manager - rpm, dpkg, Fink, something like that - will quite often
split libraries such as libxml2 into two packages; one with nothing but
the .so files which are used at run-time, and the other with the headers
and other tools needed at compile-time.
If you're using such a package manager (by whatever name), check to see if
there's an additional developer package for libxml2 and if so, if you have
installed it.
sherm--
--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org
------------------------------
Date: Mon, 12 Apr 2004 09:44:51 -0400
From: James Willmore <jwillmore@remove.adelphia.net>
Subject: Re: CPAN.pm can't find libs
Message-Id: <pan.2004.04.12.13.44.45.699086@remove.adelphia.net>
On Mon, 12 Apr 2004 09:08:03 -0400, Sherm Pendley wrote:
> kj wrote:
>
>> I'm trying to get CPAN.pm to install XML::LibXML for me. It aborts the
>> installation with a message saying that it can't find libxml2, even
>> though libxml2.so.2 is in /usr/lib.
>
> A package manager - rpm, dpkg, Fink, something like that - will quite
> often split libraries such as libxml2 into two packages; one with
> nothing but the .so files which are used at run-time, and the other with
> the headers and other tools needed at compile-time.
>
> If you're using such a package manager (by whatever name), check to see
> if there's an additional developer package for libxml2 and if so, if you
> have installed it.
Which, on a SuSE 9.0 distro, is libxml2-devel-2.5.10-32. Which contains
/usr/bin/xml2-config. Which is what the OP needs to install XML::LibXML
:-)
--
Jim
Copyright notice: all code written by the author in this post is
released under the GPL. http://www.gnu.org/licenses/gpl.txt
for more information.
a fortune quote ...
Ask not for whom the telephone bell tolls ... if thou art in the
bathtub, it tolls for thee.
------------------------------
Date: 12 Apr 2004 04:46:40 -0700
From: drubnone@yahoo.com (woof)
Subject: Re: format, stdout, with 'swrite' no hot ^
Message-Id: <7b21a826.0404120346.3441da23@posting.google.com>
The below goes. A second call to formline gets the ^<<< but
John Doe shows up again. Appears as if I must to this by hand or
redirect stdio and just use write.
my $FO_UN = " @<<<<<<<<<<<<< | ^<<<<<<<<<<<<<<<<<<<<<<<<<";
$name = 'John Doe';
$note = '11231231233 123123123123 123123123123 1231231231 123';
$psec .= swrite(<<"END", $name, $note);
$FO_UN
END
print qq/$psec\n/;
#---------------------------------------------------------------------------
sub
swrite {
my $format = shift;
$^A = "";
formline($format, @_);
formline($format, @_);
return $^A;
}
Bob Walton <invalid-email@rochester.rr.com> wrote in message news:<407982BD.3080305@rochester.rr.com>...
> woof wrote:
>
> > Monkey'd right out of perlform, I 'print' a format string to
> > to a variable with swrite like so:
> >
> >
> > $FO_UP = ' @<<<<<<<<<<<<< | ^<<<<<<<<<<<<<<<<<<<<<<<<<';
> > $name = 'John Doe';
> > $note = 'this is a very long note some would say for a 25ish space';
> > $psec .= swrite(<<"END", $name, $note);
> >
> > sub
> > swrite {
> > my $format = shift;
> > $^A = "";
> > formline($format, @_);
> > return $^A;
> > }
> >
> > Isn't the second format string "^<<<<<<<<" supposed to produce
> > multiline output?
> >
> >
> > I expect something like this:
> >
> > John Doe this is a very long
> > note some would say
> > for .....
> >
> > I get this:
> >
> > John Doe this is a very long
> >
> > Am I right or wrong? Should I expect the first or second output?
> >
> > Thanks
> >
>
> That doesn't compile as posted. *Please* copy/paste working code.
>
> If you look at:
>
> perldoc -f formline
>
> you will see where it says "You may therefore need to use
> multiple formlines to implement a single record format, just
> like the format compiler.". Some more calls of formline might give you
> what you want, although you may need to alter the format and supplied
> variables for those subsequent calls.
------------------------------
Date: 12 Apr 2004 01:58:30 -0700
From: kennyjohn00001@yahoo.com (kenny)
Subject: Re: I cann't scale gif with correctly with perlmagick.
Message-Id: <2eebf9a.0404120058.59fe98f7@posting.google.com>
Tore Aursand <tore@aursand.no> wrote in message news:<pan.2004.04.09.07.29.57.548627@aursand.no>...
> On Thu, 08 Apr 2004 21:48:25 -0700, kenny wrote:
> > Thanks correct my syntax.
>
> You should _always_ copy and paste the actual code. Don't try to rewrite
> the particular code.
>
> > but anyway, after i correct to this also face the same problem. after
> > scaling animate gif(multiple image).
>
> As previously said; I don't know much about ImageMagick (note to myself:
> make sure that I know much about ImageMagic a month from now), but are you
> sure it supports animated gifs?
I am Sure Image-Magick is support animated gifs. because when u read
animate gif with perl-magick then can write a new gif with correctly
without loss the quality image.
but the problem is when the scale method apply to animate gif. the gif
after scale look like incorrectly.... sometime u will see the white
dot.
me suspect is image-magick don scale image with smoothly and leave
some blank/white dot after scaling at the image. because scale ratio
don return accuracy.
eg: first image of animate gif size is 280X 280 scale to 80%. so
image size now is 224X224.
second image of animate gif size is 150X 150 scale to 80%. so image
size now is 187.5X187.5. but..... in the pixel, we don't have .5
pixel. so problem is come. so maybe second image scale to 187X187 or
188X188. this situation maybe will leave white dot/blank dot....
so any solution to solve this problem or not?
------------------------------
Date: Mon, 12 Apr 2004 05:36:01 -0500
From: John Bokma <postmaster@castleamber.com>
Subject: Re: I cann't scale gif with correctly with perlmagick.
Message-Id: <407a7116$0$24349$58c7af7e@news.kabelfoon.nl>
kenny wrote:
> second image of animate gif size is 150X 150 scale to 80%. so image
> size now is 187.5X187.5. but..... in the pixel, we don't have .5
> pixel. so problem is come. so maybe second image scale to 187X187 or
> 188X188. this situation maybe will leave white dot/blank dot....
>
> so any solution to solve this problem or not?
Doesn't GIF animation not rely very much on transparency?. Maybe scaling
each individual GIF frame and reassembling it into an animation, and
optimizing it, gives the right result.
--
John personal page: http://johnbokma.com/
Experienced Perl / Java developer available - http://castleamber.com/
------------------------------
Date: Mon, 12 Apr 2004 01:17:30 -0500
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: perldoc incompetence: perlre /s
Message-Id: <slrnc7kd3q.3l0.tadmc@magna.augustmail.com>
Xah Lee <xah@xahlee.org> wrote:
> fuck Perl coders.
The overwhelming majority of Perl coders are men.
You are most bold coming out like that in such a public forum!
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Mon, 12 Apr 2004 13:52:46 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: perldoc incompetence: perlre /s
Message-Id: <x74qrpgv69.fsf@mail.sysarch.com>
>>>>> "XL" == Xah Lee <xah@xahlee.org> writes:
XL> Fucking no mention of it. Fuck Perl and fuck Perl coders.
you prove your stupidity everytime you post here. you hate perl and yet
always seem to go back to it. why? do none of your other vaunter
languages have the power to solve the problems you have? do you not have
the brains to use them properly? ever heard of turing compability? ever
heard about writing algorithms in any language? so why do you insist on
banging your head against the perl wall? must be 'cause you are autistic
or something. get a helmet then and work in a padded room. you will be
safe from perl and we will be safe from you.
now stay away from perl and this group. the world will be a better place
that way.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.stemsystems.com
--Perl Consulting, Stem Development, Systems Architecture, Design and Coding-
Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
------------------------------
Date: Mon, 12 Apr 2004 09:54:40 -0400
From: James Willmore <jwillmore@remove.adelphia.net>
Subject: Re: perldoc incompetence: perlre /s
Message-Id: <pan.2004.04.12.13.54.34.892440@remove.adelphia.net>
On Sun, 11 Apr 2004 19:59:03 -0700, Xah Lee wrote:
> today i'm writing some perl code involving regex. I wanted to find out
> exactly what is /s (whitespace) is defined. So i did "perldoc -t
> perlre".
(from perlre)
NAME
perlre - Perl regular expressions
DESCRIPTION
This page describes the syntax of regular expressions in Perl.
....
s Treat string as single line. That is, change "." to match any
character whatsoever, even a newline, which normally it would not
match.
The "/s" and "/m" modifiers both override the $* setting. That is,
no matter what $* contains, "/s" without "/m" will force "^" to
match only at the beginning of the string and "$" to match only at
the end (or just before a newline at the end) of the string.
Together, as /ms, they let the "." match any character whatsoever,
while still allowing "^" and "$" to match, respectively, just
after and just before newlines within the string.
....
In addition, Perl defines the following:
\w Match a "word" character (alphanumeric plus "_") \W Match a
non-"word" character
\s Match a whitespace character
\S Match a non-whitespace character
\d Match a digit character
\D Match a non-digit character
\pP Match P, named property. Use \p{Prop} for longer names. \PP
Match non-P
\X Match eXtended Unicode "combining character sequence",
equivalent to (?:\PM\pM*)
\C Match a single C char (octet) even under Unicode.
NOTE: breaks up characters into their UTF-8 bytes, so you may
end up with malformed pieces of UTF-8. Unsupported in
lookbehind.
(end quote of perlre)
> Fucking no mention of it. Fuck Perl and fuck Perl coders.
Yes, there is :-) Both ways (/s and \s) :-)
HTH
--
Jim
Copyright notice: all code written by the author in this post is
released under the GPL. http://www.gnu.org/licenses/gpl.txt
for more information.
a fortune quote ...
The older a man gets, the farther he had to walk to school as a
boy.
------------------------------
Date: 12 Apr 2004 07:28:23 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: regex not matching high end
Message-Id: <c5dgen$65$1@mamenchi.zrz.TU-Berlin.DE>
Anatase <anatase@cablespeed.com> wrote in comp.lang.perl.misc:
> if(!($input2 =~ /[a-zA-Z]{4,12}/))
> {
> print "try the input again\n";
> Usernamesub();
> }
>
> aaa - does not match so steps in
> aaaa - match so steps past
> aaaaaaaaaaaaa - 13+ should step in - but instead steps past
No. There *are* 12 characters in "aaaaaaaaaaaaa", and the regex matches
them.
To get the behavior you expect you must anchor the regex on both ends:
/^[a-zA-Z]{4,12}$/
Anno
------------------------------
Date: Mon, 12 Apr 2004 02:36:27 -0500
From: John Bokma <postmaster@castleamber.com>
Subject: Re: regex not matching high end
Message-Id: <407a46ff$0$24345$58c7af7e@news.kabelfoon.nl>
Anatase wrote:
> if(!($input2 =~ /[a-zA-Z]{4,12}/))
> {
> print "try the input again\n";
> Usernamesub();
> }
>
> aaa - does not match so steps in
> aaaa - match so steps past
> aaaaaaaaaaaaa - 13+ should step in - but instead steps past
because it matches, it contains at least 12 a's.
/^[a-zA-Z]{4,12}$/
is probably what you want, at least 4, max 12 letters.
Also, if(!...) { is often more readable written as unless () {
--
John personal page: http://johnbokma.com/
Experienced Perl / Java developer available - http://castleamber.com/
------------------------------
Date: Mon, 12 Apr 2004 06:52:59 -0400
From: Chris Mattern <matternc@comcast.net>
Subject: Re: regex not matching high end
Message-Id: <v8adnbNLkbSR6Ofd4p2dnA@comcast.com>
Anatase wrote:
> if(!($input2 =~ /[a-zA-Z]{4,12}/))
> {
> print "try the input again\n";
> Usernamesub();
> }
>
> aaa - does not match so steps in
> aaaa - match so steps past
> aaaaaaaaaaaaa - 13+ should step in - but instead steps past
Well, of course it does. The string has twelve "a"s in it.
It has some more "a"s after that, but that doesn't change the
fact that it has twelve "a"s.
>
> I'm using active states perl 5.8 it seems.
--
Christopher Mattern
"Which one you figure tracked us?"
"The ugly one, sir."
"...Could you be more specific?"
------------------------------
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 6388
***************************************
