Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bigtex.cactus.org!james
From: james@bigtex.cactus.org (James Van Artsdalen)
Newsgroups: gnu.bash.bug
Subject: Re: ISI68K (and also UMAX)
Message-ID: <8906150043.AA05027@bigtex.cactus.org>
Date: 15 Jun 89 00:43:54 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 30

> Date: Wed, 14 Jun 89 00:01:53 EDT
> From: composer@bu-cs.bu.edu (Jeff Kellem)

|   Date: Tue, 13 Jun 89 22:41:47 EST
|   From: ray@gibbs.physics.purdue.edu (Ray Moody)

|       Bash gives off "billiyons and billiyons" of compiler warnings as
|   it compiles, but it works anyway.  I plan to fix this someday.

> Actually, I believe that James Van Artsdalen is doing a good amount of
> work towards cleaning up that aspect.

Trying anyway.  Turns out to be quite difficult.  bash will not work
on anything where sizeof int != sizeof char *, or where initialized
char variables take up less than sizeof int bytes, and probably not
with a really smart globally optimizing compiler (I wouldn't recommend
using gcc's inlining just yet).

I have a set of ANSI function prototypes and a complete set of extern
declarations for variables.  My eventual goal is to be able to compile
with PCC (one that supports void) without warnings, and to compile
with gcc -Wall without warnings.

The function types have had to undergo a lot of changes, and some of
the variables have also needed new types.  I don't know when or how
the function prototypes will get merged in to the real source - it may
be a while.
---
James R. Van Artsdalen          james@bigtex.cactus.org   "Live Free or Die"
Dell Computer Co    9505 Arboretum Blvd Austin TX 78759         512-338-8789