Re: Guile 1.4.1 w/ guile-oops 1.0.2

[Thien-Thi Nguyen <ttn@giblet.glug.org>]

   From: Michael Carmack <karmak@karmak.org>
   Date: Fri, 6 Sep 2002 08:21:18 +0000

   Is guile-oops/1.0.2 not intended to be used with guile/1.4.1?

more like guile-snarf invocation changing should be considered a bug,
especially in light of 1.4.x goal of compatibility (mea culpa)!  i've
since reverted the behavior for 1.4.2, but that's not available yet.
1.4.1.84, a snapshot precursor, is available under:

  http://www.glug.org/tmp/2002-09/

if you are building guile-1.4.1 from source, you can replace
guile-snarf.in (note the .in extension) w/ the file appended below.

thi


___________________________________________
#!/bin/sh
# Extract the initialization actions from source files.
#
#  Copyright (C) 1996, 97, 98, 99, 2000, 2001, 2002 Free Software Foundation, Inc.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2, or (at your option)
# any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this software; see the file COPYING.  If not, write to
# the Free Software Foundation, Inc., 59 Temple Place, Suite 330,
# Boston, MA 02111-1307 USA

# Commentary:

# Usage: guile-snarf --help
# Usage: guile-snarf --version
#
# Usage: guile-snarf [-o OUTFILE] [CPP-ARGS ...]
#
# Process CPP-ARGS using the C pre-processor and some other programs.
# Write output to a file named OUTFILE or to the standard output when no
# OUTFILE has been specified or when OUTFILE is "-".  CPP-ARGS should
# include an input filename.
#
# If there are errors during processing, delete OUTFILE and exit with
# non-zero status.
#
# During snarfing, the pre-processor macro SCM_MAGIC_SNARFER is
# defined.
#
# If env var CPP is set, use its value instead of the C pre-processor
# determined at Guile configure-time: "@CPP@".

# Code:

## support

do_the_snarf ()                         # writes stdout
{
${cpp} -DSCM_MAGIC_SNARFER "$@" > ${temp} && cpp_ok_p=true
sed -e '/^ *SCM__I/!d' -e 's/^ *SCM__I//' -e 's/ *SCM__D.*$//' ${temp}
}

## main

# process command line
if [ x"$1" = x--help ] ; then
    @AWK@ '/^#.Commentary:/,/^#.Code:/' $0 | grep -v Code: \
        | sed -e 1,2d -e 's/^. *//g'
    exit 0
fi
if [ x"$1" = x--version ] ; then
    echo "guile-snarf @VERSION@"
    exit 0
fi
if [ x"$1" = x-o ]
    then outfile=$2 ; shift ; shift
    else outfile="-"
fi

# set vars and handler -- handle CPP override
cpp_ok_p=false
temp="/tmp/snarf.$$"
if [ x"$CPP" = x ] ; then cpp="@CPP@" ; else cpp="$CPP" ; fi

trap "rm -f $temp" 0 1 2 15

if [ ! "$outfile" = "-" ]; then
    do_the_snarf "$@" > $outfile
else
    do_the_snarf "$@"
fi

# zonk outfile if errors occurred
if $cpp_ok_p ; then
    exit 0
else
    [ ! "$outfile" = "-" ] && rm -f $outfile
    exit 1
fi

# guile-snarf ends here


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile