| To: | "Daniel Jacobowitz" <dan@debian.org> |
|---|---|
| Subject: | Re: Function pointers and #defines |
| From: | "Justin Carlson" <justinca@cs.cmu.edu> |
| Date: | 30 May 2002 12:58:44 -0700 |
| Cc: | linux-mips@oss.sgi.com |
| In-reply-to: | <20020530195052.GA10587@branoic.them.org> |
| References: | <1022787167.14210.472.camel@ldt-sj3-022.sj.broadcom.com> <20020530195052.GA10587@branoic.them.org> |
| Sender: | owner-linux-mips@oss.sgi.com |
On Thu, 2002-05-30 at 12:50, Daniel Jacobowitz wrote: > > 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? > > At a guess, this prevents taking the address of the function > unintentionally... But if you're writing code in such a way that the compiler type checking doesn't flag this, you deserve what you get. (IMHO, of course. :) -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, Hartvig Ekner |
|---|---|
| Next by Date: | Re: Function pointers and #defines, Daniel Jacobowitz |
| Previous by Thread: | Re: Function pointers and #defines, Daniel Jacobowitz |
| Next by Thread: | Re: Function pointers and #defines, Kevin D. Kissell |
| Indexes: | [Date] [Thread] [Top] [All Lists] |