gnupic: Re: [gnupic] Re: gpasm `extern' vs `global' (new feature patch)
Subject:
Re: [gnupic] Re: gpasm `extern' vs `global' (new feature patch)
From:
"Scott Dattalo" ####@####.####
Date:
17 Dec 2005 23:21:52 +0000
Message-Id: <61090.71.139.33.203.1134861608.squirrel@71.139.33.203>
On Fri, 2005-12-16 at 12:26 +0000, Ian Jackson wrote:
> I've been using my patched 0.13.3-1 gputils for the past few months
> and this has been working well. I would like to suggest that my
> patch, or something like it, be included in the next gputils release.
Ian,
I like the idea of your patch. I too dislike having to doubly define
everything. The only concern I have with your patch is that it makes gpasm
incompatible with MPASM in some way. It doesn't appear that this is the
case, but do you know for sure? Just to be clear, your patch allows one to
write:
EXTERN some_variable
This statement may reside in an include file which can be included by all
sources in the project; even the one that declares 'some_variable'.
Without your patch, gpasm will produce an error if the "EXTERN
some_variable" and "GLOBAL some_variable" statements are seen while
assembling a file.
I suppose if you write code for gpasm making use of this feature and then
attempt to assemble it with MPASM that it will fail? Is this true? Does it
matter?
Can someone with easy access to mpasm try assembling this:
;---- test file
extern temp
global temp
end
;---- end test file
Scott
