google_hash 0.8.1 → 0.8.2

data/ext/{sparsehash-1.8.1 → sparsehash-2.0.2}/doc/sparse_hash_set.html

@@ -87,7 +87,7 @@ details.)
 
 <pre>
 #include &lt;iostream&gt;
-#include &lt;google/sparse_hash_set&gt;
+#include &lt;sparsehash/sparse_hash_set&gt;
 
 using google::sparse_hash_set;      // namespace where class lives by default
 using std::cout;
@@ -588,7 +588,7 @@ None.
    <tt>Unordered Associative Container</tt> (tr1)
 </TD>
 <TD VAlign=top>
-   If the key exists in the map, returns the index of the bucket
+   If the key exists in the set, returns the index of the bucket
    containing the given key, otherwise, return the bucket the key
    would be inserted into.
    This value may be passed to <tt>begin(size_type)</tt> and
@@ -1120,7 +1120,8 @@ key_type&amp; k) const</pre>
 
 <TR>
 <TD VAlign=top>
-   <tt>bool write_metadata(FILE *fp)</tt>
+   <tt>template &lt;ValueSerializer, OUTPUT&gt;
+       bool serialize(ValueSerializer serializer, OUTPUT *fp)</tt>
 </TD>
 <TD VAlign=top>
    <tt>sparse_hash_set</tt>
@@ -1132,7 +1133,8 @@ key_type&amp; k) const</pre>
 
 <TR>
 <TD VAlign=top>
-   <tt>bool read_metadata(FILE *fp)</tt>
+   <tt>template &lt;ValueSerializer, INPUT&gt;
+       bool unserialize(ValueSerializer serializer, INPUT *fp)</tt>
 </TD>
 <TD VAlign=top>
    <tt>sparse_hash_set</tt>
@@ -1144,7 +1146,7 @@ key_type&amp; k) const</pre>
 
 <TR>
 <TD VAlign=top>
-   <tt>bool write_nopointer_data(FILE *fp)</tt>
+   <tt>NopointerSerializer</tt>
 </TD>
 <TD VAlign=top>
    <tt>sparse_hash_set</tt>
@@ -1154,6 +1156,42 @@ key_type&amp; k) const</pre>
 </TD>
 </TR>
 
+<TR>
+<TD VAlign=top>
+   <tt>bool write_metadata(FILE *fp)</tt>
+</TD>
+<TD VAlign=top>
+   <tt>sparse_hash_set</tt>
+</TD>
+<TD VAlign=top>
+   DEPRECATED.  <A HREF="#new">See below</A>.
+</TD>
+</TR>
+
+<TR>
+<TD VAlign=top>
+   <tt>bool read_metadata(FILE *fp)</tt>
+</TD>
+<TD VAlign=top>
+   <tt>sparse_hash_set</tt>
+</TD>
+<TD VAlign=top>
+   DEPRECATED.  <A HREF="#new">See below</A>.
+</TD>
+</TR>
+
+<TR>
+<TD VAlign=top>
+   <tt>bool write_nopointer_data(FILE *fp)</tt>
+</TD>
+<TD VAlign=top>
+   <tt>sparse_hash_set</tt>
+</TD>
+<TD VAlign=top>
+   DEPRECATED.  <A HREF="#new">See below</A>.
+</TD>
+</TR>
+
 <TR>
 <TD VAlign=top>
    <tt>bool read_nopointer_data(FILE *fp)</tt>
@@ -1162,7 +1200,7 @@ key_type&amp; k) const</pre>
    <tt>sparse_hash_set</tt>
 </TD>
 <TD VAlign=top>
-   <A HREF="#new">See below</A>.
+   DEPRECATED.  <A HREF="#new">See below</A>.
 </TD>
 </TR>
 
@@ -1228,12 +1266,35 @@ Container</tt> requirements, but are specific to
 </TD>
 </TR>
 
+<TR>
+<TD VAlign=top>
+   <tt>template &lt;ValueSerializer, OUTPUT&gt;
+       bool serialize(ValueSerializer serializer, OUTPUT *fp)</tt>
+</TD>
+<TD VAlign=top>
+   Emit a serialization of the hash_set to a stream.
+   See <A HREF="#io">below</A>.
+</TD>
+</TR>
+
+<TR>
+<TD VAlign=top>
+   <tt>template &lt;ValueSerializer, INPUT&gt;
+       bool unserialize(ValueSerializer serializer, INPUT *fp)</tt>
+</TD>
+<TD VAlign=top>
+   Read in a serialization of a hash_set from a stream, replacing the
+   existing hash_set contents with the serialized contents.
+   See <A HREF="#io">below</A>.
+</TD>
+</TR>
+
 <TR>
 <TD VAlign=top>
    <tt>bool write_metadata(FILE *fp)</tt>
 </TD>
 <TD VAlign=top>
-   Write hashtable metadata to <tt>fp</tt>.  See <A HREF="#io">below</A>.
+   This function is DEPRECATED.  See <A HREF="#io">below</A>.
 </TD>
 </TR>
 
@@ -1242,7 +1303,7 @@ Container</tt> requirements, but are specific to
    <tt>bool read_metadata(FILE *fp)</tt>
 </TD>
 <TD VAlign=top>
-   Read hashtable metadata from <tt>fp</tt>.  See <A HREF="#io">below</A>.
+   This function is DEPRECATED.  See <A HREF="#io">below</A>.
 </TD>
 </TR>
 
@@ -1251,8 +1312,7 @@ Container</tt> requirements, but are specific to
    <tt>bool write_nopointer_data(FILE *fp)</tt>
 </TD>
 <TD VAlign=top>
-   Write hashtable contents to <tt>fp</tt>.  This is valid only if the
-   hashtable key and value are "plain" data.  See <A HREF="#io">below</A>.
+   This function is DEPRECATED.  See <A HREF="#io">below</A>.
 </TD>
 </TR>
 
@@ -1261,8 +1321,7 @@ Container</tt> requirements, but are specific to
    <tt>bool read_nopointer_data(FILE *fp)</tt>
 </TD>
 <TD VAlign=top>
-   Read hashtable contents to <tt>fp</tt>.  This is valid only if the
-   hashtable key and value are "plain" data.  See <A HREF="#io">below</A>.
+   This function is DEPRECATED.  See <A HREF="#io">below</A>.
 </TD>
 </TR>
 
@@ -1330,65 +1389,121 @@ insertion but no hashtable entries can be deleted until
 <h3><A NAME=io>Input/Output</A></h3>
 
 <p>It is possible to save and restore <tt>sparse_hash_set</tt> objects
-to disk.  Storage takes place in two steps.  The first writes the
-hashtable metadata.  The second writes the actual data.</p>
-
-<p>To write a hashtable to disk, first call <tt>write_metadata()</tt>
-on an open file pointer.  This saves the hashtable information in a
-byte-order-independent format.</p>
-
-<p>After the metadata has been written to disk, you must write the
-actual data stored in the hash-set to disk.  If both the key and data
-are "simple" enough, you can do this by calling
-<tt>write_nopointer_data()</tt>.  "Simple" data is data that can be
-safely copied to disk via <tt>fwrite()</tt>.  Native C data types fall
-into this category, as do structs of native C data types.  Pointers
-and STL objects do not.</p>
-
-<p>Note that <tt>write_nopointer_data()</tt> does not do any endian
-conversion.  Thus, it is only appropriate when you intend to read the
-data on the same endian architecture as you write the data.</p>
+to an arbitrary stream (such as a disk file) using the
+<tt>serialize()</tt> and <tt>unserialize()</tt> methods.</p>
+
+<p>Each of these methods takes two arguments: a <i>serializer</i>,
+which says how to write hashtable items to disk, and a <i>stream</i>,
+which can be a C++ stream (<tt>istream</tt> or its subclasses for
+input, <tt>ostream</tt> or its subclasses for output), a
+<tt>FILE*</tt>, or a user-defined type (as described below).</p>
+
+<p>The <it>serializer</i> is a functor that takes a stream and a
+single hashtable element (a <tt>value_type</tt>) and copies the
+hashtable element to the stream (for <tt>serialize()</tt>) or fills
+the hashtable element contents from the stream (for
+<tt>unserialize()</tt>), and returns true on success or false on
+error.  The copy-in and copy-out functions can be provided in a single
+functor.  Here is a sample serializer that read/writes a hashtable
+element for a string hash_set to a <tt>FILE*</tt>:</p>
+
+<pre>
+struct StringSerializer {
+  bool operator()(FILE* fp, const std::string&amp; value) const {
+    assert(value.length() &lt;= 255);   // we only support writing small strings
+    const unsigned char size = value.length();
+    if (fwrite(&amp;size, 1, 1, fp) != 1)
+      return false;
+    if (fwrite(value.data(), size, 1, fp) != 1)
+      return false;
+    return true;
+  }
+  bool operator()(FILE* fp, std::string* value) const {
+    unsigned char size;    // all strings are &lt;= 255 chars long
+    if (fread(&amp;size, 1, 1, fp) != 1)
+      return false;
+    char* buf = new char[size];
+    if (fread(buf, size, 1, fp) != 1) {
+      delete[] buf;
+      return false;
+    }
+    new(value) string(buf, size);
+    delete[] buf;
+    return true;
+  }
+};
+</pre>
 
-<p>If you cannot use <tt>write_nopointer_data()</tt> for any reason,
-you can write the data yourself by iterating over the
-<tt>sparse_hash_set</tt> with a <tt>const_iterator</tt> and writing
-the key and data in any manner you wish.</p>
-
-<p>To read the hashtable information from disk, first you must create
-a <tt>sparse_hash_set</tt> object.  Then open a file pointer to point
-to the saved hashtable, and call <tt>read_metadata()</tt>.  If you
-saved the data via <tt>write_nopointer_data()</tt>, you can follow the
-<tt>read_metadata()</tt> call with a call to
-<tt>read_nopointer_data()</tt>.  This is all that is needed.</p>
-
-<p>If you saved the data through a custom write routine, you must call
-a custom read routine to read in the data.  To do this, iterate over
-the <tt>sparse_hash_set</tt> with an <tt>iterator</tt>; this operation
-is sensical because the metadata has already been set up.  For each
-iterator item, you can read the key and value from disk, and set it
-appropriately.  You will need to do a <tt>const_cast</tt> on the
-iterator, since <tt>*it</tt> is always <tt>const</tt>.  The
-code might look like this:</p>
+<p>Here is the functor being used in code (error checking omitted):</p>
 <pre>
-   for (sparse_hash_set&lt;int*&gt;::iterator it = ht.begin();
-        it != ht.end(); ++it) {
-       const_cast&lt;int*&gt;(*it) = new int;
-       fread(const_cast&lt;int*&gt;(*it), sizeof(int), 1, fp);
-   }
+   sparse_hash_set&lt;string&gt; myset = CreateSet();
+   FILE* fp = fopen("hashtable.data", "w");
+   myset.serialize(StringSerializer(), fp);
+   fclose(fp);
+
+   sparse_hash_set&lt;string&gt; myset2;
+   FILE* fp_in = fopen("hashtable.data", "r");
+   myset2.unserialize(StringSerializer(), fp_in);
+   fclose(fp_in);
+   assert(myset == myset2);
 </pre>
 
-<p>Here's another example, where the item stored in the hash-set is
-a C++ object with a non-trivial constructor.  In this case, you must
-use "placement new" to construct the object at the correct memory
-location.</p>
+<p><b>Important note:</b> the code above uses placement-new to
+instantiate the <tt>string</tt>.  This is <i>required</i> for any
+non-POD type.  The value_type passed in to the unserializer
+points to garbage memory, so it is not safe to assign to it directly
+if doing so causes a destructor to be called.</p>
+
+<p>Also note that this example serializer can only serialize to a
+FILE*.  If you want to also be able to use this serializer with C++
+streams, you will need to write two more overloads of
+<tt>operator()</tt>'s, one that reads from an <tt>istream</tt>, and
+one that writes to an <tt>ostream</tt>.  Likewise if you want to
+support serializing to a custom class.</p>
+
+<p>If the key is "simple" enough, you can use the pre-supplied functor
+<tt>NopointerSerializer</tt>.  This copies the hashtable data using
+the equivalent of a <tt>memcpy<></tt>.  Native C data types can be
+serialized this way, as can structs of native C data types.  Pointers
+and STL objects cannot.</p>
+
+<p>Note that <tt>NopointerSerializer()</tt> does not do any endian
+conversion.  Thus, it is only appropriate when you intend to read the
+data on the same endian architecture as you write the data.</p>
+
+<p>If you wish to serialize to your own stream type, you can do so by
+creating an object which supports two methods:</p>
 <pre>
-   for (sparse_hash_set&lt;ComplicatedClass&gt;::iterator it = ht.begin();
-        it != ht.end(); ++it) {
-       int ctor_arg;  // ComplicatedClass takes an int as its constructor arg
-       fread(&ctor_arg, sizeof(int), 1, fp);
-       new (const_cast&lt;ComplicatedClass*&gt;(&(*it))) ComplicatedClass(ctor_arg);
-   }
+   bool Write(const void* data, size_t length);
+   bool Read(void* data, size_t length);
 </pre>
+<p><tt>Write()</tt> writes <tt>length</tt> bytes of <tt>data</tt> to a
+stream (presumably a stream owned by the object), while
+<tt>Read()</tt> reads <tt>data</tt> bytes from the stream into
+<tt>data</tt>.  Both return true on success or false on error.</p>
+
+<p>To unserialize a hashtable from a stream, you wil typically create
+a new <tt>sparse_hash_set</tt> object, then call <tt>unserialize()</tt>
+on it.  <tt>unserialize()</tt> destroys the old contents of the
+object.  You must pass in the appropriate <tt>ValueSerializer</tt> for
+the data being read in.</p>
+
+<p>Both <tt>serialize()</tt> and <tt>unserialize()</tt> return
+<tt>true</tt> on success, or <tt>false</tt> if there was an error
+streaming the data.</p>
+
+<p>Note that <tt>serialize()</tt> is not a const method, since it
+purges deleted elements before serializing.  It is not safe to
+serialize from two threads at once, without synchronization.</p>
+
+<p>NOTE: older versions of <tt>sparse_hash_set</tt> provided a
+different API, consisting of <tt>read_metadata()</tt>,
+<tt>read_nopointer_data()</tt>, <tt>write_metadata()</tt>,
+<tt>write_nopointer_data()</tt>.  Writing to disk consisted of a call
+to <tt>write_metadata()</tt> followed by
+<tt>write_nopointer_data()</tt> (if the hash data was POD) or a custom
+loop over the hashtable buckets to write the data (otherwise).
+Reading from disk was similar.  Prefer the new API for new code.</p>
 
 
 <h3><A NAME=iter>Validity of Iterators</A></h3>

data/ext/{sparsehash-1.8.1 → sparsehash-2.0.2}/doc/sparsetable.html

@@ -78,7 +78,7 @@ persistent.</p>
 <h3>Example</h3>
 
 <pre>
-#include &lt;google/sparsetable&gt;
+#include &lt;sparsehash/sparsetable&gt;
 
 using google::sparsetable;      // namespace where class lives by default
 

data/ext/{sparsehash-1.8.1 → sparsehash-2.0.2}/experimental/example.c

@@ -1,3 +1,4 @@
+#include <sparsehash/internal/sparseconfig.h>
 #include <stdlib.h>
 #include <stdio.h>
 #include <assert.h>

data/ext/{sparsehash-1.8.1 → sparsehash-2.0.2}/experimental/libchash.c

@@ -118,6 +118,7 @@
  *  is defined correctly for your machine!  (5 for 32 bit words, 6 for 64).
  */
 
+#include <sparsehash/internal/sparseconfig.h>
 #include <stdlib.h>
 #include <stdio.h>
 #include <string.h>       /* for strcmp, memcmp, etc */

data/ext/{sparsehash-1.8.1 → sparsehash-2.0.2}/experimental/libchash.h

@@ -115,6 +115,7 @@
  *        from disk.
  */
 
+#include <sparsehash/internal/sparseconfig.h>
 #include <sys/types.h>         /* includes definition of "ulong", we hope */
 #define ulong u_long
 

data/ext/sparsehash-2.0.2/install-sh

@@ -0,0 +1,520 @@
+#!/bin/sh
+# install - install a program, script, or datafile
+
+scriptversion=2009-04-28.21; # UTC
+
+# This originates from X11R5 (mit/util/scripts/install.sh), which was
+# later released in X11R6 (xc/config/util/install.sh) with the
+# following copyright and license.
+#
+# Copyright (C) 1994 X Consortium
+#
+# Permission is hereby granted, free of charge, to any person obtaining a copy
+# of this software and associated documentation files (the "Software"), to
+# deal in the Software without restriction, including without limitation the
+# rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
+# sell copies of the Software, and to permit persons to whom the Software is
+# furnished to do so, subject to the following conditions:
+#
+# The above copyright notice and this permission notice shall be included in
+# all copies or substantial portions of the Software.
+#
+# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL THE
+# X CONSORTIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN
+# AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNEC-
+# TION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+#
+# Except as contained in this notice, the name of the X Consortium shall not
+# be used in advertising or otherwise to promote the sale, use or other deal-
+# ings in this Software without prior written authorization from the X Consor-
+# tium.
+#
+#
+# FSF changes to this file are in the public domain.
+#
+# Calling this script install-sh is preferred over install.sh, to prevent
+# `make' implicit rules from creating a file called install from it
+# when there is no Makefile.
+#
+# This script is compatible with the BSD install script, but was written
+# from scratch.
+
+nl='
+'
+IFS=" ""	$nl"
+
+# set DOITPROG to echo to test this script
+
+# Don't use :- since 4.3BSD and earlier shells don't like it.
+doit=${DOITPROG-}
+if test -z "$doit"; then
+  doit_exec=exec
+else
+  doit_exec=$doit
+fi
+
+# Put in absolute file names if you don't have them in your path;
+# or use environment vars.
+
+chgrpprog=${CHGRPPROG-chgrp}
+chmodprog=${CHMODPROG-chmod}
+chownprog=${CHOWNPROG-chown}
+cmpprog=${CMPPROG-cmp}
+cpprog=${CPPROG-cp}
+mkdirprog=${MKDIRPROG-mkdir}
+mvprog=${MVPROG-mv}
+rmprog=${RMPROG-rm}
+stripprog=${STRIPPROG-strip}
+
+posix_glob='?'
+initialize_posix_glob='
+  test "$posix_glob" != "?" || {
+    if (set -f) 2>/dev/null; then
+      posix_glob=
+    else
+      posix_glob=:
+    fi
+  }
+'
+
+posix_mkdir=
+
+# Desired mode of installed file.
+mode=0755
+
+chgrpcmd=
+chmodcmd=$chmodprog
+chowncmd=
+mvcmd=$mvprog
+rmcmd="$rmprog -f"
+stripcmd=
+
+src=
+dst=
+dir_arg=
+dst_arg=
+
+copy_on_change=false
+no_target_directory=
+
+usage="\
+Usage: $0 [OPTION]... [-T] SRCFILE DSTFILE
+   or: $0 [OPTION]... SRCFILES... DIRECTORY
+   or: $0 [OPTION]... -t DIRECTORY SRCFILES...
+   or: $0 [OPTION]... -d DIRECTORIES...
+
+In the 1st form, copy SRCFILE to DSTFILE.
+In the 2nd and 3rd, copy all SRCFILES to DIRECTORY.
+In the 4th, create DIRECTORIES.
+
+Options:
+     --help     display this help and exit.
+     --version  display version info and exit.
+
+  -c            (ignored)
+  -C            install only if different (preserve the last data modification time)
+  -d            create directories instead of installing files.
+  -g GROUP      $chgrpprog installed files to GROUP.
+  -m MODE       $chmodprog installed files to MODE.
+  -o USER       $chownprog installed files to USER.
+  -s            $stripprog installed files.
+  -t DIRECTORY  install into DIRECTORY.
+  -T            report an error if DSTFILE is a directory.
+
+Environment variables override the default commands:
+  CHGRPPROG CHMODPROG CHOWNPROG CMPPROG CPPROG MKDIRPROG MVPROG
+  RMPROG STRIPPROG
+"
+
+while test $# -ne 0; do
+  case $1 in
+    -c) ;;
+
+    -C) copy_on_change=true;;
+
+    -d) dir_arg=true;;
+
+    -g) chgrpcmd="$chgrpprog $2"
+	shift;;
+
+    --help) echo "$usage"; exit $?;;
+
+    -m) mode=$2
+	case $mode in
+	  *' '* | *'	'* | *'
+'*	  | *'*'* | *'?'* | *'['*)
+	    echo "$0: invalid mode: $mode" >&2
+	    exit 1;;
+	esac
+	shift;;
+
+    -o) chowncmd="$chownprog $2"
+	shift;;
+
+    -s) stripcmd=$stripprog;;
+
+    -t) dst_arg=$2
+	shift;;
+
+    -T) no_target_directory=true;;
+
+    --version) echo "$0 $scriptversion"; exit $?;;
+
+    --)	shift
+	break;;
+
+    -*)	echo "$0: invalid option: $1" >&2
+	exit 1;;
+
+    *)  break;;
+  esac
+  shift
+done
+
+if test $# -ne 0 && test -z "$dir_arg$dst_arg"; then
+  # When -d is used, all remaining arguments are directories to create.
+  # When -t is used, the destination is already specified.
+  # Otherwise, the last argument is the destination.  Remove it from $@.
+  for arg
+  do
+    if test -n "$dst_arg"; then
+      # $@ is not empty: it contains at least $arg.
+      set fnord "$@" "$dst_arg"
+      shift # fnord
+    fi
+    shift # arg
+    dst_arg=$arg
+  done
+fi
+
+if test $# -eq 0; then
+  if test -z "$dir_arg"; then
+    echo "$0: no input file specified." >&2
+    exit 1
+  fi
+  # It's OK to call `install-sh -d' without argument.
+  # This can happen when creating conditional directories.
+  exit 0
+fi
+
+if test -z "$dir_arg"; then
+  trap '(exit $?); exit' 1 2 13 15
+
+  # Set umask so as not to create temps with too-generous modes.
+  # However, 'strip' requires both read and write access to temps.
+  case $mode in
+    # Optimize common cases.
+    *644) cp_umask=133;;
+    *755) cp_umask=22;;
+
+    *[0-7])
+      if test -z "$stripcmd"; then
+	u_plus_rw=
+      else
+	u_plus_rw='% 200'
+      fi
+      cp_umask=`expr '(' 777 - $mode % 1000 ')' $u_plus_rw`;;
+    *)
+      if test -z "$stripcmd"; then
+	u_plus_rw=
+      else
+	u_plus_rw=,u+rw
+      fi
+      cp_umask=$mode$u_plus_rw;;
+  esac
+fi
+
+for src
+do
+  # Protect names starting with `-'.
+  case $src in
+    -*) src=./$src;;
+  esac
+
+  if test -n "$dir_arg"; then
+    dst=$src
+    dstdir=$dst
+    test -d "$dstdir"
+    dstdir_status=$?
+  else
+
+    # Waiting for this to be detected by the "$cpprog $src $dsttmp" command
+    # might cause directories to be created, which would be especially bad
+    # if $src (and thus $dsttmp) contains '*'.
+    if test ! -f "$src" && test ! -d "$src"; then
+      echo "$0: $src does not exist." >&2
+      exit 1
+    fi
+
+    if test -z "$dst_arg"; then
+      echo "$0: no destination specified." >&2
+      exit 1
+    fi
+
+    dst=$dst_arg
+    # Protect names starting with `-'.
+    case $dst in
+      -*) dst=./$dst;;
+    esac
+
+    # If destination is a directory, append the input filename; won't work
+    # if double slashes aren't ignored.
+    if test -d "$dst"; then
+      if test -n "$no_target_directory"; then
+	echo "$0: $dst_arg: Is a directory" >&2
+	exit 1
+      fi
+      dstdir=$dst
+      dst=$dstdir/`basename "$src"`
+      dstdir_status=0
+    else
+      # Prefer dirname, but fall back on a substitute if dirname fails.
+      dstdir=`
+	(dirname "$dst") 2>/dev/null ||
+	expr X"$dst" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
+	     X"$dst" : 'X\(//\)[^/]' \| \
+	     X"$dst" : 'X\(//\)$' \| \
+	     X"$dst" : 'X\(/\)' \| . 2>/dev/null ||
+	echo X"$dst" |
+	    sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
+		   s//\1/
+		   q
+		 }
+		 /^X\(\/\/\)[^/].*/{
+		   s//\1/
+		   q
+		 }
+		 /^X\(\/\/\)$/{
+		   s//\1/
+		   q
+		 }
+		 /^X\(\/\).*/{
+		   s//\1/
+		   q
+		 }
+		 s/.*/./; q'
+      `
+
+      test -d "$dstdir"
+      dstdir_status=$?
+    fi
+  fi
+
+  obsolete_mkdir_used=false
+
+  if test $dstdir_status != 0; then
+    case $posix_mkdir in
+      '')
+	# Create intermediate dirs using mode 755 as modified by the umask.
+	# This is like FreeBSD 'install' as of 1997-10-28.
+	umask=`umask`
+	case $stripcmd.$umask in
+	  # Optimize common cases.
+	  *[2367][2367]) mkdir_umask=$umask;;
+	  .*0[02][02] | .[02][02] | .[02]) mkdir_umask=22;;
+
+	  *[0-7])
+	    mkdir_umask=`expr $umask + 22 \
+	      - $umask % 100 % 40 + $umask % 20 \
+	      - $umask % 10 % 4 + $umask % 2
+	    `;;
+	  *) mkdir_umask=$umask,go-w;;
+	esac
+
+	# With -d, create the new directory with the user-specified mode.
+	# Otherwise, rely on $mkdir_umask.
+	if test -n "$dir_arg"; then
+	  mkdir_mode=-m$mode
+	else
+	  mkdir_mode=
+	fi
+
+	posix_mkdir=false
+	case $umask in
+	  *[123567][0-7][0-7])
+	    # POSIX mkdir -p sets u+wx bits regardless of umask, which
+	    # is incompatible with FreeBSD 'install' when (umask & 300) != 0.
+	    ;;
+	  *)
+	    tmpdir=${TMPDIR-/tmp}/ins$RANDOM-$$
+	    trap 'ret=$?; rmdir "$tmpdir/d" "$tmpdir" 2>/dev/null; exit $ret' 0
+
+	    if (umask $mkdir_umask &&
+		exec $mkdirprog $mkdir_mode -p -- "$tmpdir/d") >/dev/null 2>&1
+	    then
+	      if test -z "$dir_arg" || {
+		   # Check for POSIX incompatibilities with -m.
+		   # HP-UX 11.23 and IRIX 6.5 mkdir -m -p sets group- or
+		   # other-writeable bit of parent directory when it shouldn't.
+		   # FreeBSD 6.1 mkdir -m -p sets mode of existing directory.
+		   ls_ld_tmpdir=`ls -ld "$tmpdir"`
+		   case $ls_ld_tmpdir in
+		     d????-?r-*) different_mode=700;;
+		     d????-?--*) different_mode=755;;
+		     *) false;;
+		   esac &&
+		   $mkdirprog -m$different_mode -p -- "$tmpdir" && {
+		     ls_ld_tmpdir_1=`ls -ld "$tmpdir"`
+		     test "$ls_ld_tmpdir" = "$ls_ld_tmpdir_1"
+		   }
+		 }
+	      then posix_mkdir=:
+	      fi
+	      rmdir "$tmpdir/d" "$tmpdir"
+	    else
+	      # Remove any dirs left behind by ancient mkdir implementations.
+	      rmdir ./$mkdir_mode ./-p ./-- 2>/dev/null
+	    fi
+	    trap '' 0;;
+	esac;;
+    esac
+
+    if
+      $posix_mkdir && (
+	umask $mkdir_umask &&
+	$doit_exec $mkdirprog $mkdir_mode -p -- "$dstdir"
+      )
+    then :
+    else
+
+      # The umask is ridiculous, or mkdir does not conform to POSIX,
+      # or it failed possibly due to a race condition.  Create the
+      # directory the slow way, step by step, checking for races as we go.
+
+      case $dstdir in
+	/*) prefix='/';;
+	-*) prefix='./';;
+	*)  prefix='';;
+      esac
+
+      eval "$initialize_posix_glob"
+
+      oIFS=$IFS
+      IFS=/
+      $posix_glob set -f
+      set fnord $dstdir
+      shift
+      $posix_glob set +f
+      IFS=$oIFS
+
+      prefixes=
+
+      for d
+      do
+	test -z "$d" && continue
+
+	prefix=$prefix$d
+	if test -d "$prefix"; then
+	  prefixes=
+	else
+	  if $posix_mkdir; then
+	    (umask=$mkdir_umask &&
+	     $doit_exec $mkdirprog $mkdir_mode -p -- "$dstdir") && break
+	    # Don't fail if two instances are running concurrently.
+	    test -d "$prefix" || exit 1
+	  else
+	    case $prefix in
+	      *\'*) qprefix=`echo "$prefix" | sed "s/'/'\\\\\\\\''/g"`;;
+	      *) qprefix=$prefix;;
+	    esac
+	    prefixes="$prefixes '$qprefix'"
+	  fi
+	fi
+	prefix=$prefix/
+      done
+
+      if test -n "$prefixes"; then
+	# Don't fail if two instances are running concurrently.
+	(umask $mkdir_umask &&
+	 eval "\$doit_exec \$mkdirprog $prefixes") ||
+	  test -d "$dstdir" || exit 1
+	obsolete_mkdir_used=true
+      fi
+    fi
+  fi
+
+  if test -n "$dir_arg"; then
+    { test -z "$chowncmd" || $doit $chowncmd "$dst"; } &&
+    { test -z "$chgrpcmd" || $doit $chgrpcmd "$dst"; } &&
+    { test "$obsolete_mkdir_used$chowncmd$chgrpcmd" = false ||
+      test -z "$chmodcmd" || $doit $chmodcmd $mode "$dst"; } || exit 1
+  else
+
+    # Make a couple of temp file names in the proper directory.
+    dsttmp=$dstdir/_inst.$$_
+    rmtmp=$dstdir/_rm.$$_
+
+    # Trap to clean up those temp files at exit.
+    trap 'ret=$?; rm -f "$dsttmp" "$rmtmp" && exit $ret' 0
+
+    # Copy the file name to the temp name.
+    (umask $cp_umask && $doit_exec $cpprog "$src" "$dsttmp") &&
+
+    # and set any options; do chmod last to preserve setuid bits.
+    #
+    # If any of these fail, we abort the whole thing.  If we want to
+    # ignore errors from any of these, just make sure not to ignore
+    # errors from the above "$doit $cpprog $src $dsttmp" command.
+    #
+    { test -z "$chowncmd" || $doit $chowncmd "$dsttmp"; } &&
+    { test -z "$chgrpcmd" || $doit $chgrpcmd "$dsttmp"; } &&
+    { test -z "$stripcmd" || $doit $stripcmd "$dsttmp"; } &&
+    { test -z "$chmodcmd" || $doit $chmodcmd $mode "$dsttmp"; } &&
+
+    # If -C, don't bother to copy if it wouldn't change the file.
+    if $copy_on_change &&
+       old=`LC_ALL=C ls -dlL "$dst"	2>/dev/null` &&
+       new=`LC_ALL=C ls -dlL "$dsttmp"	2>/dev/null` &&
+
+       eval "$initialize_posix_glob" &&
+       $posix_glob set -f &&
+       set X $old && old=:$2:$4:$5:$6 &&
+       set X $new && new=:$2:$4:$5:$6 &&
+       $posix_glob set +f &&
+
+       test "$old" = "$new" &&
+       $cmpprog "$dst" "$dsttmp" >/dev/null 2>&1
+    then
+      rm -f "$dsttmp"
+    else
+      # Rename the file to the real destination.
+      $doit $mvcmd -f "$dsttmp" "$dst" 2>/dev/null ||
+
+      # The rename failed, perhaps because mv can't rename something else
+      # to itself, or perhaps because mv is so ancient that it does not
+      # support -f.
+      {
+	# Now remove or move aside any old file at destination location.
+	# We try this two ways since rm can't unlink itself on some
+	# systems and the destination file might be busy for other
+	# reasons.  In this case, the final cleanup might fail but the new
+	# file should still install successfully.
+	{
+	  test ! -f "$dst" ||
+	  $doit $rmcmd -f "$dst" 2>/dev/null ||
+	  { $doit $mvcmd -f "$dst" "$rmtmp" 2>/dev/null &&
+	    { $doit $rmcmd -f "$rmtmp" 2>/dev/null; :; }
+	  } ||
+	  { echo "$0: cannot unlink or rename $dst" >&2
+	    (exit 1); exit 1
+	  }
+	} &&
+
+	# Now rename the file to the real destination.
+	$doit $mvcmd "$dsttmp" "$dst"
+      }
+    fi || exit 1
+
+    trap '' 0
+  fi
+done
+
+# Local variables:
+# eval: (add-hook 'write-file-hooks 'time-stamp)
+# time-stamp-start: "scriptversion="
+# time-stamp-format: "%:y-%02m-%02d.%02H"
+# time-stamp-time-zone: "UTC"
+# time-stamp-end: "; # UTC"
+# End: