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 lemburg
Recipients alexandre.vassalotti, blaisorblade, christian.heimes, lemburg, pitrou, rhettinger, skip.montanaro
Date 2009-01-02.14:57:14
SpamBayes Score 5.445268e-09
Marked as misclassified No
Message-id <495E2B49.8020702@egenix.com>
In-reply-to <1230850791.65.0.79634207218.issue4753@psf.upfronthosting.co.za>
Content
On 2009-01-01 23:59, Antoine Pitrou wrote:
> Antoine Pitrou <pitrou@free.fr> added the comment:
> 
> I've updated the comments as per Alexandre's request, added support for
> SUN CC, and fixed the generation script to use the new filename.

Since the patch heavily relies on the compiler doing the right
thing (which esp. GCC often doesn't, unfortunately), I think that the
opcode dispatch code should only be enabled via a configure option.

This is safer than enabling the support unconditionally for GCC and
the SUN Pro C compiler, since it is rather likely that some GCC versions
have bugs which could render Python unusable if compiled with the
dispatching support enabled.

A configure option also has the additional benefit that you can enable
the support for compilers which support the syntax, but are not included
in the hard-coded list of compilers included in the patch.
History
Date User Action Args
2009-01-02 14:57:16lemburgsetrecipients: + lemburg, skip.montanaro, rhettinger, pitrou, christian.heimes, alexandre.vassalotti, blaisorblade
2009-01-02 14:57:15lemburglinkissue4753 messages
2009-01-02 14:57:14lemburgcreate