| To: | linux-mips@oss.sgi.com |
|---|---|
| Subject: | Function pointers and #defines |
| From: | "Justin Carlson" <justinca@cs.cmu.edu> |
| Date: | 30 May 2002 12:32:47 -0700 |
| Sender: | owner-linux-mips@oss.sgi.com |
A fair number of places in the headers, we have stuff like this: void (*_some_fn)(int arg1, int arg2); #define some_fn(arg1, arg2) _some_fn(arg1, arg2) Why do we do this, as opposed to: void (*some_fn)(int arg1, int arg2); Both syntaxes result in being able to say some_fn(1, 2); but the latter is both clearer and shorter. Is there some deep, mystical C reason that we use the former, or did someone do it that way a long time ago and no one has changed it? -Justin |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: cross-compiler for MIPS_RedHat7.1_Release-01.00 on Atlas/4Kc using RH7.3-i386 host, David Christensen |
|---|---|
| Next by Date: | Re: cross-compiler for MIPS_RedHat7.1_Release-01.00 on Atlas/4Kc using RH7.3-i386 host, Hartvig Ekner |
| Previous by Thread: | Cache flushing, take 2, Justin Carlson |
| Next by Thread: | Re: Function pointers and #defines, Daniel Jacobowitz |
| Indexes: | [Date] [Thread] [Top] [All Lists] |