Re: Macros to check for variables, next try

2002-04-15 Thread Paul Eggert
> From: Peter Eisentraut <[EMAIL PROTECTED]> > Date: Mon, 15 Apr 2002 22:14:44 -0400 (EDT) > Any ideas out there? Here's an idea: In general, require that the user supply both the variable name and the complete C-language declaration, including the variable name and trailing semicolon. However

Re: Macros to check for variables, next try

2002-04-15 Thread Peter Eisentraut
Andreas Schwab writes: > Peter Eisentraut <[EMAIL PROTECTED]> writes: > > |> # AC_LANG_VAR_LINK_TRY(C)(TYPE, VARIABLE, [INCLUDES]) > |> # --- > |> m4_define([AC_LANG_VAR_LINK_TRY(C)], > |> [AC_LANG_PROGRAM( > |> [AC_INCLUDES_DEFAULT([$3]) > |> exter

Re: 2.53a m4sh.at:74 failure

2002-04-15 Thread Patrick Welche
In testsuite: cat >test/test-1.as <<'_ATEOF' AS_INIT if false; then AS_UNSET([LINENO]) fi _AS_PREPARE echo "Line: $LINENO" grep 'Line: .*LINENO' $[0] >/dev/null || AS_ERROR([cannot find original script]) exit 0 _ATEOF But once run with testsuite -v -x 15 % cat testsuite.dir/015/test/test

CONGRATULATIONS!! YOU WON!!

2002-04-15 Thread syndy cash
Title: CONGRATULATIONS!! YOU WON!!   CONGRATULATIONS!! YOU WON!!   YOUR FREE MEMBERSHIP & FREE SOFTWARE!! PLUS - Your FREE Cell Phone!!   CHECK IT OUT! 2500+ MEMBERS A MONTH!!   ALL new members that come into the club COMPANY WIDE will go under YOU.   A true VERTICAL downline. YOU ca