This is the mail archive of the
guile@sourceware.cygnus.com
mailing list for the Guile project.
Re: Guile docstrings---should Guile code be ANSI C compatible?
Mikael Djurfeldt <mdj@mdj.nada.kth.se> writes:
> "Greg J. Badros" <gjb@cs.washington.edu> writes:
>
> > Mikael Djurfeldt <mdj@mdj.nada.kth.se> writes:
> >
> > <snip>
> >
> > > But in configure.in, I've written:
> > >
> > > AC_CACHE_CHECK([for long longs], scm_cv_long_longs,
> > > AC_TRY_COMPILE(,
> > > [long long a],
> > > scm_cv_long_longs=yes,
> > > scm_cv_long_longs=no))
> > > if test "$scm_cv_long_longs" = yes; then
> > > AC_DEFINE(HAVE_LONG_LONGS)
> > > fi
> > >
> > > I hope I'm strictly using it only if HAVE_LONG_LONGS is defined.
> >
> > I don't see where that guard is for the uses around __scm.h:114.
>
<snip>
> Greg, did you find any more unguarded occurrences?
Not that I recall-- the only warnings that come up w/ -pedantic are asm
and "long long" warnings...
Greg