Re: ANNOUNCE: port of alpha bison-2.0

[Paul Eggert]

"Eli Zaretskii" <address@hidden> writes:

> +#if !HAVE_WORKING_VFORK && !HAVE_WORKING_FORK
> +  /* On non posix systems that lack vfork or vork
> +     m4 must be explicitly spwaned to process bison output. */
> +  run_m4 (filter_fd);
> +#endif

I'd rather do this as a more-generic call without an ifdef.  Something
like this, say:

   end_of_output_subpipe (pid, argv, filter_fd);

This would require adding a no-op function to the mainline code,
but that's OK.

>  # ifdef MSDOS
> -   /* MS DOS. */
> -#  define TAB_EXT    "_tab"
> -#  define OUTPUT_EXT ".out"

My understanding (correct me if I'm wrong) is that the vast majority
of Microsoft Windows installations now support longer file names --
particularly when we're thinking about the people likely to run Bison
-- so I don't see the need to require support for shorter, nonstandard
file names.  On the contrary, I see them as causing them more trouble
than they'd cure, even on Microsoft Windows installations, since you'd
need to parameterize Makefiles etc. depending on whether you're
running in an 8.3 file system.