/[pcre]/code/trunk/maint/README
ViewVC logotype

Diff of /code/trunk/maint/README

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 579 by ph10, Wed Nov 24 17:39:25 2010 UTC revision 583 by ph10, Tue Jan 11 16:49:55 2011 UTC
# Line 35  MultiStage2.py   A Python script that ge Line 35  MultiStage2.py   A Python script that ge
35                   Unicode web site. Run this script in the "maint" directory.                   Unicode web site. Run this script in the "maint" directory.
36                   The generated file contains the tables for a 2-stage lookup                   The generated file contains the tables for a 2-stage lookup
37                   of Unicode properties.                   of Unicode properties.
38    
39  pcre_chartables.c.non-standard  pcre_chartables.c.non-standard
40                   This is a set of character tables that came from a Windows                   This is a set of character tables that came from a Windows
41                   system. It has characters greater than 128 that are set as                   system. It has characters greater than 128 that are set as
42                   spaces, amongst other things. I kept it so that it can be                   spaces, amongst other things. I kept it so that it can be
43                   used for testing from time to time.                   used for testing from time to time.
44    
45  README           This file.  README           This file.
46    
# Line 117  distribution for a new release. Line 117  distribution for a new release.
117  . Test with valgrind by running "RunTest valgrind". There is also "RunGrepTest  . Test with valgrind by running "RunTest valgrind". There is also "RunGrepTest
118    valgrind", though that takes quite a long time.    valgrind", though that takes quite a long time.
119    
120  . Test with the emulated memmove() function by undefining HAVE_MEMMOVE and  . It is possible to test with the emulated memmove() function by undefining
121    HAVE_BCOPY in config.h. You may see a number of "pcre_memmove defined but not    HAVE_MEMMOVE and HAVE_BCOPY in config.h, though I do not do this often. You
122    used" warnings for the modules in which there is no call to memmove(). These    may see a number of "pcre_memmove defined but not used" warnings for the
123    can be ignored.    modules in which there is no call to memmove(). These can be ignored.
124    
125  . Documentation: check AUTHORS, COPYING, ChangeLog (check version and date),  . Documentation: check AUTHORS, COPYING, ChangeLog (check version and date),
126    INSTALL, LICENCE, NEWS (check version and date), NON-UNIX-USE, and README.    INSTALL, LICENCE, NEWS (check version and date), NON-UNIX-USE, and README.
127    Many of these won't need changing, but over the long term things do change.    Many of these won't need changing, but over the long term things do change.
128    
129  . Man pages: Check all man pages for \ not followed by e or f or " because  . I used to test new releases myself on a number of different operating
130    that indicates a markup error. However, there is one exception: pcredemo.3,    systems, using different compilers as well. For example, on Solaris it is
131    which is created from the pcredemo.c program. It contains three instances    helpful to test using Sun's cc compiler as a change from gcc. Adding
132    of \\n.    -xarch=v9 to the cc options does a 64-bit test, but it also needs -S 64 for
133      pcretest to increase the stack size for test 2. Since I retired I can no
134  . When the release is built, test it on a number of different operating    longer do this, but instead I rely on putting out release candidates for
135    systems if possible, and using different compilers as well. For example,    folks on the pcre-dev list to test.
   on Solaris it is helpful to test using Sun's cc compiler as a change from  
   gcc. Adding -xarch=v9 to the cc options does a 64-bit test, but it also  
   needs -S 64 for pcretest to increase the stack size for test 2.  
136    
137    
138  Making a PCRE release  Making a PCRE release
139  =====================  =====================
140    
141  Run PrepareRelease and commit the files that it changes (by removing trailing  Run PrepareRelease and commit the files that it changes (by removing trailing
142  spaces). Then run "make distcheck" to create the tarballs and the zipball.  spaces). The first thing this script does is to run CheckMan on the man pages;
143  Double-check with "svn status", then create an SVN tagged copy:  if it finds any markup errors, it reports them and then aborts.
144    
145    Once PrepareRelease has run clean, run "make distcheck" to create the tarballs
146    and the zipball. Double-check with "svn status", then create an SVN tagged
147    copy:
148    
149    svn copy svn://vcs.exim.org/pcre/code/trunk \    svn copy svn://vcs.exim.org/pcre/code/trunk \
150             svn://vcs.exim.org/pcre/code/tags/pcre-8.xx             svn://vcs.exim.org/pcre/code/tags/pcre-8.xx
# Line 204  others are relatively new. Line 205  others are relatively new.
205    
206  . Unicode  . Unicode
207    
208      * There has been a request for direct support of 16-bit characters and
209        UTF-16 (Bugzilla #1049). However, since Unicode is moving beyond purely
210        16-bit characters, is this worth it at all? One possible way of handling
211        16-bit characters would be to "load" them in the same way that UTF-8
212        characters are loaded. Another possibility is to provide a set of
213        translation functions, and build an index during translation so that the
214        returned offsets can automatically be translated (using the index) after a
215        match.
216    
217    * A different approach to Unicode might be to use a typedef to do everything    * A different approach to Unicode might be to use a typedef to do everything
218      in unsigned shorts instead of unsigned chars. Actually, we'd have to have a      in unsigned shorts instead of unsigned chars. Actually, we'd have to have a
219      new typedef to distinguish data from bits of compiled pattern that are in      new typedef to distinguish data from bits of compiled pattern that are in
220      bytes, I think. There would need to be conversion functions in and out. I      bytes, I think. There would need to be conversion functions in and out. I
221      don't think this is particularly trivial - and anyway, Unicode now has      don't think this is particularly trivial - and anyway, Unicode now has
222      characters that need more than 16 bits, so is this at all sensible?      characters that need more than 16 bits, so is this at all sensible? I
223        suspect not.
   * There has been a request for direct support of 16-bit characters and  
     UTF-16. However, since Unicode is moving beyond purely 16-bit characters,  
     is this worth it at all? One possible way of handling 16-bit characters  
     would be to "load" them in the same way that UTF-8 characters are loaded.  
224    
225  . Allow errorptr and erroroffset to be NULL. I don't like this idea.  . Allow errorptr and erroroffset to be NULL. I don't like this idea.
226    
# Line 315  others are relatively new. Line 321  others are relatively new.
321  Philip Hazel  Philip Hazel
322  Email local part: ph10  Email local part: ph10
323  Email domain: cam.ac.uk  Email domain: cam.ac.uk
324  Last updated: 24 November 2010  Last updated: 12 January 2011

Legend:
Removed from v.579  
changed lines
  Added in v.583

  ViewVC Help
Powered by ViewVC 1.1.5