 |
 |
Macro Errors
|
|
|
|
|
Mac Elite
Join Date: Jan 2001
Location: New York
Status:
Offline
|
|
Is there some simple tool to check for macro conflicts(such as using the same macro name), checking your source files against libraries?
|
|
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: Jan 2001
Location: New York
Status:
Offline
|
|
A command-line tool would fit the job perfectly...
|
|
|
| |
|
|
|
|
|
|
|
Grizzled Veteran
Join Date: Sep 2000
Location: Springfield, MA
Status:
Offline
|
|
In particular grep is what you're looking for.
|
|
We hope your rules and wisdom choke you / Now we are one in everlasting peace
-- Radiohead, Exit Music (for a film)
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: Jan 2001
Location: New York
Status:
Offline
|
|
Originally posted by Mactoid:
<STRONG>In particular grep is what you're looking for.</STRONG>
I thought grep was just for searching a file. But it won't automatically check out header files linked to by one of my files, right? I guess I should go check out its man pages now...
|
|
|
| |
|
|
|
|
|
|
|
Dedicated MacNNer
Join Date: Jan 2001
Location: Boulder, CO, USA
Status:
Offline
|
|
Originally posted by davecom:
<STRONG>Is there some simple tool to check for macro conflicts(such as using the same macro name), checking your source files against libraries?</STRONG>
Is the compiler's complaint about redefinition of a macro not sufficient?
|
|
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: Jan 2001
Location: New York
Status:
Offline
|
|
Originally posted by aleph_null:
<STRONG>
Is the compiler's complaint about redefinition of a macro not sufficient?</STRONG>
I want a tool that does it before compile-time.
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
 
|
|
|
Forum Rules
|
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|
Top
