FM / html

/usr/share/doc/pcre-devel/html

Name	Size	Mode	Actions
index.html	7677	0644	edit dl rm
NON-AUTOTOOLS-BUILD.txt	31359	0644	edit dl rm
pcre-config.html	3659	0644	edit dl rm
pcre.html	10382	0644	edit dl rm
pcre16.html	16214	0644	edit dl rm
pcre32.html	16098	0644	edit dl rm
pcreapi.html	135354	0644	edit dl rm
pcrebuild.html	22838	0644	edit dl rm
pcrecallout.html	11675	0644	edit dl rm
pcrecompat.html	9791	0644	edit dl rm
pcrecpp.html	14395	0644	edit dl rm
pcredemo.html	16192	0644	edit dl rm
pcregrep.html	37847	0644	edit dl rm
pcrejit.html	22103	0644	edit dl rm
pcrelimits.html	3195	0644	edit dl rm
pcrematching.html	10898	0644	edit dl rm
pcrepartial.html	23592	0644	edit dl rm
pcrepattern.html	140690	0644	edit dl rm
pcreperform.html	7827	0644	edit dl rm
pcreposix.html	12139	0644	edit dl rm
pcreprecompile.html	7399	0644	edit dl rm
pcresample.html	3784	0644	edit dl rm
pcrestack.html	9594	0644	edit dl rm
pcresyntax.html	16694	0644	edit dl rm
pcretest.html	52187	0644	edit dl rm
pcreunicode.html	11444	0644	edit dl rm
pcre_assign_jit_stack.html	2541	0644	edit dl rm
pcre_compile.html	4735	0644	edit dl rm
pcre_compile2.html	4907	0644	edit dl rm
pcre_config.html	3938	0644	edit dl rm
pcre_copy_named_substring.html	2359	0644	edit dl rm
pcre_copy_substring.html	2115	0644	edit dl rm
pcre_dfa_exec.html	5969	0644	edit dl rm
pcre_exec.html	5059	0644	edit dl rm
pcre_free_study.html	1231	0644	edit dl rm
pcre_free_substring.html	1283	0644	edit dl rm
pcre_free_substring_list.html	1289	0644	edit dl rm
pcre_fullinfo.html	5150	0644	edit dl rm
pcre_get_named_substring.html	2460	0644	edit dl rm
pcre_get_stringnumber.html	1773	0644	edit dl rm
pcre_get_stringtable_entries.html	2062	0644	edit dl rm
pcre_get_substring.html	2243	0644	edit dl rm
pcre_get_substring_list.html	2198	0644	edit dl rm
pcre_jit_exec.html	4814	0644	edit dl rm
pcre_jit_stack_alloc.html	1720	0644	edit dl rm
pcre_jit_stack_free.html	1279	0644	edit dl rm
pcre_maketables.html	1397	0644	edit dl rm
pcre_pattern_to_host_byte_order.html	1960	0644	edit dl rm
pcre_refcount.html	1442	0644	edit dl rm
pcre_study.html	2146	0644	edit dl rm
pcre_utf16_to_host_byte_order.html	2033	0644	edit dl rm
pcre_utf32_to_host_byte_order.html	2033	0644	edit dl rm
pcre_version.html	1172	0644	edit dl rm
README.txt	45548	0644	edit dl rm

Edit: /usr/share/doc/pcre-devel/html/pcresample.html (3784B)

<html>
<head>
<title>pcresample specification</title>
</head>
<body bgcolor="#FFFFFF" text="#00005A" link="#0066FF" alink="#3399FF" vlink="#2222BB">
<h1>pcresample man page</h1>

Return to the <a href="index.html">PCRE index page</a>.


This page is part of the PCRE HTML documentation. It was generated automatically
from the original man page. If there is any nonsense in it, please consult the
man page, in case the conversion went wrong.
 
 
PCRE SAMPLE PROGRAM
 

A simple, complete demonstration program, to get you started with using PCRE,
is supplied in the file pcredemo.c in the PCRE distribution. A listing of
this program is given in the
<a href="pcredemo.html">pcredemo</a>
documentation. If you do not have a copy of the PCRE distribution, you can save
this listing to re-create pcredemo.c.


The demonstration program, which uses the original PCRE 8-bit library, compiles
the regular expression that is its first argument, and matches it against the
subject string in its second argument. No PCRE options are set, and default
character tables are used. If matching succeeds, the program outputs the
portion of the subject that matched, together with the contents of any captured
substrings.


If the -g option is given on the command line, the program then goes on to
check for further matches of the same regular expression in the same subject
string. The logic is a little bit tricky because of the possibility of matching
an empty string. Comments in the code explain what is going on.


If PCRE is installed in the standard include and library directories for your
operating system, you should be able to compile the demonstration program using
this command:
<pre>
 gcc -o pcredemo pcredemo.c -lpcre
</pre>
If PCRE is installed elsewhere, you may need to add additional options to the
command line. For example, on a Unix-like system that has PCRE installed in
/usr/local, you can compile the demonstration program using a command
like this:
<pre>
 gcc -o pcredemo -I/usr/local/include pcredemo.c -L/usr/local/lib -lpcre
</pre>
In a Windows environment, if you want to statically link the program against a
non-dll pcre.a file, you must uncomment the line that defines PCRE_STATIC
before including pcre.h, because otherwise the pcre_malloc() and
pcre_free() exported functions will be declared
__declspec(dllimport), with unwanted results.


Once you have compiled and linked the demonstration program, you can run simple
tests like this:
<pre>
 ./pcredemo 'cat|dog' 'the cat sat on the mat'
 ./pcredemo -g 'cat|dog' 'the dog sat on the cat'
</pre>
Note that there is a much more comprehensive test program, called
<a href="pcretest.html">pcretest,</a>
which supports many more facilities for testing regular expressions and both
PCRE libraries. The
<a href="pcredemo.html">pcredemo</a>
program is provided as a simple coding example.


If you try to run
<a href="pcredemo.html">pcredemo</a>
when PCRE is not installed in the standard library directory, you may get an
error like this on some operating systems (e.g. Solaris):
<pre>
 ld.so.1: a.out: fatal: libpcre.so.0: open failed: No such file or directory
</pre>
This is caused by the way shared library support works on those systems. You
need to add
<pre>
 -R/usr/local/lib
</pre>
(for example) to the compile command to get round this problem.

 
AUTHOR
 

Philip Hazel
 
University Computing Service
 
Cambridge CB2 3QH, England.
 

 
REVISION
 

Last updated: 10 January 2012
 
Copyright &copy; 1997-2012 University of Cambridge.
 

Return to the <a href="index.html">PCRE index page</a>.

cmd: