Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mcvax!ukc!dcl-cs!bath63!sc_dra
From: sc_dra@ux63.bath.ac.uk (Dave Allum)
Newsgroups: comp.sys.atari.st
Subject: Re: Megamax inline assembly woes (solution)
Message-ID: <1155@bath63.ux63.bath.ac.uk>
Date: Mon, 18-May-87 04:15:25 EDT
Article-I.D.: bath63.1155
Posted: Mon May 18 04:15:25 1987
Date-Received: Wed, 20-May-87 03:29:08 EDT
References: <8705120723.AA17281@cory.Berkeley.EDU>
Reply-To: sc_dra@ux63.bath.ac.uk (Dave Allum)
Organization: SWURCC, University of Bath, UK
Lines: 14
Summary: Declaration in loop allowed by Megamax

In article <8705120723.AA17281@cory.Berkeley.EDU> dillon@CORY.BERKELEY.EDU (Matt Dillon) writes:
>:Declaring variables both at the top of a function and in a loop:
>:	while ( condition )  {
>:		register char	*cp;	/* <<< megamax won't allow this */
>:	}
>	This is standard C.  If megamax doesn't allow it, megamax shouldn't
>be on the shelves.  Every major programmer I know uses this construction.

Megemax _does_ allow this - just checked it out (must confess I didn't 
realise it was standard C until now).  I have V1.1 so I guess it could 
have been a problem with the earlier release.  Anyone still on V1
care to check it?

Dave Allum.