From: Davide Libenzi <davidel@xmailserver.org>
To: Hua Zhong <huaz@cs.columbia.edu>
Cc: linux-kernel@vger.kernel.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: linux/macros.h(new) and linux/list.h(mod) ...
Date: Thu, 05 Jul 2001 15:06:24 -0700 (PDT) [thread overview]
Message-ID: <XFMail.20010705150624.davidel@xmailserver.org> (raw)
In-Reply-To: <200107052154.RAA07008@razor.cs.columbia.edu>
On 05-Jul-2001 Hua Zhong wrote:
>
> Doesn't it add more overhead? I think using inline functions are much
> better.
> Yes you have to define it for different types (char, short, int, long,
> signed/unsigned).
Yes it does.
Personally I know that min, max, etc... are macros and I never use unary
operators inside.
Maybe a "unsafe" __max() and a "safe" max() could coexist.
- Davide
next prev parent reply other threads:[~2001-07-05 22:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-05 20:57 linux/macros.h(new) and linux/list.h(mod) Davide Libenzi
2001-07-05 21:31 ` David Woodhouse
2001-07-05 21:45 ` Davide Libenzi
2001-07-05 21:54 ` Hua Zhong
2001-07-05 21:58 ` David Woodhouse
2001-07-05 22:20 ` Hua Zhong
2001-07-05 22:06 ` Davide Libenzi [this message]
2001-07-05 22:10 ` J . A . Magallon
2001-07-05 22:33 ` Daniel Phillips
2001-07-05 22:43 ` David Woodhouse
2001-07-05 22:53 ` Davide Libenzi
2001-07-05 23:23 ` J . A . Magallon
2001-07-05 22:57 ` Alan Cox
2001-07-05 23:05 ` Matthew Dharm
2001-07-05 23:07 ` Alan Cox
2001-07-05 23:08 ` David Woodhouse
2001-07-06 1:51 ` Arnaldo Carvalho de Melo
2001-07-05 23:21 ` Davide Libenzi
[not found] ` <0107060149080M.03760@starship>
2001-07-05 23:54 ` Daniel Phillips
2001-07-06 17:38 ` Neil Booth
2001-07-06 22:02 ` Arnaldo Carvalho de Melo
2001-07-05 22:03 ` Kai Germaschewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=XFMail.20010705150624.davidel@xmailserver.org \
--to=davidel@xmailserver.org \
--cc=dwmw2@infradead.org \
--cc=huaz@cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.