| www.delorie.com/archives/browse.cgi | search |
| Sender: | antony AT mail02 DOT syd DOT optusnet DOT com DOT au |
| Message-ID: | <3964C164.22648267@mira.net> |
| Date: | Fri, 07 Jul 2000 03:27:00 +1000 |
| From: | Antony Suter <antony AT mira DOT net> |
| X-Mailer: | Mozilla 4.73 [en] (X11; I; Linux 2.2.16yb i686) |
| X-Accept-Language: | en |
| MIME-Version: | 1.0 |
| To: | pgcc AT delorie DOT com |
| Subject: | Re: What's up with this?? |
| References: | <D1674834F25BD3118B3208002BB90CD450DEBF AT yen DOT crl DOT dec DOT com> |
| Reply-To: | pgcc AT delorie DOT com |
What is the two line explanation as to why it cant be:-
{ \
/* stuff */ \
}
George France wrote:
>
> It is not moot; it is so that inline macro's expand properly. See the gcc or
> linux-kernel archives for more details.
>
> -----Original Message-----
> From: RH [mailto:rdh AT wt DOT net]
>
> I have been wondering why in the world is code mostly in macros of the form.
>
> do {
> /*stuff*/
> while(0);
>
> I don't get this... Seems stupid and pointless. So I would just like an
> explination and if its moot now a days, why don't people start removing
> them...
--
- Antony Suter (antony AT mira DOT net) 'Examiner'
- "And how do you store the nuclear equivalent of the universal
solvent?"
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |