➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Alexander.Belopolsky
Recipients Alexander.Belopolsky, arigo, belopolsky, bob.ippolito, fredrik_j, mark.dickinson, pitrou, rhettinger, theller
Date 2010-03-05.02:46:27
SpamBayes Score 1.4803993e-07
Marked as misclassified No
Message-id <d38f5331003041845x78579b23q1b2ee463636679b1@mail.gmail.com>
In-reply-to <1267756194.38.0.279570235514.issue887237@psf.upfronthosting.co.za>
Content 
I would like to hear from Thomas before introducing macros in this
code.  I tried to follow the style of cfield.c which shows similar
code duplication.

There are also some questions that need to be answered before
polishing the code.

1. Should mixed arithmetics be supported?
2. Should we do anything special about floating point operations?
Wrapping them in PyFPE_START/STOP_PROTECT?
3. Should we support in-place operations?
4. Bitwise operations on integers?

On Thu, Mar 4, 2010 at 9:29 PM, Raymond Hettinger
<report@bugs.python.org> wrote:
>
> Raymond Hettinger <rhettinger@users.sourceforge.net> added the comment:
>
> Look at Modules/operator.c for example of an effective use of macros to minimize code duplication.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue887237>
> _______________________________________
>
History
Date User Action Args
2010-03-05 02:46:29Alexander.Belopolskysetrecipients: + Alexander.Belopolsky, arigo, theller, rhettinger, bob.ippolito, mark.dickinson, belopolsky, pitrou, fredrik_j
2010-03-05 02:46:28Alexander.Belopolskylinkissue887237 messages
2010-03-05 02:46:27Alexander.Belopolskycreate