Thread View: gnu.bash.bug
1 messages
1 total messages
Started by James Van Artsdalen
Thu, 15 Jun 1989 00:43
Re: ISI68K (and also UMAX)
Author: James Van Artsdalen
Date: Thu, 15 Jun 1989 00:43
Date: Thu, 15 Jun 1989 00:43
30 lines
1783 bytes
1783 bytes
> 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
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads