On Thu, Apr 05, 2001 at 09:06:20AM -0400, Bart Trojanowski wrote:
> So you ask: "why not just use a { ... } to define a macro". I don't
> remember the case for this but I know it's there. It has to do with a
> complicated if/else structure where a simple {} breaks.
It's for eating the semi-colon after the macro invocation.
Tim.
*/
--EUwkhXZbCcD53YNR
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE6zG9PONXnILZ4yVIRAn46AJ9qAOqXytZwZ5LmJj9B4o8tNgzefwCfV94b
TJcxDB2GBbVHXSN1g6PA9Cw=
=YurY
-----END PGP SIGNATURE-----
--EUwkhXZbCcD53YNR--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/