Muhammad Alkarouri <malkaro...@gmail.com> added the comment: On 15 October 2010 06:52, Martin v. Löwis <rep...@bugs.python.org> wrote: > > Martin v. Löwis <mar...@v.loewis.de> added the comment: > > Interesting. I'd like to propose than that this is resolved as "won't fix", > i.e. embedding Python into Delphi is declared as just not supported (or using > floating-point operations in such an environment is not supported).
The problem is defining what does "such an environment" mean. It is not necessarily Delphi, as this can happen whenever the FPU control word is changed by an embedding application. Kiriakos makes a good point. The underlying issue is that Python make certain assumptions about the FPU control words, and there are probably other global assumptions lurking elsewhere. As I see it, the easiest solution is to document these assumptions as and when they are found. Then it becomes the responsibility of the hosting application to satisfy them. Delphi already has to accomodate Python C heritage, for example by defining functions used from Python with the C calling convention. This would be just one more thing to remember, and in fact can be done inside the Python4Delphi libraries once the Python behaviour is defined and documented. Also, banning floating-point operations is not a solution in my opinion because Python libraries (standard and external) do not have such a distinction. So an unknown of unexpected libraries (like json) would break. And large parts of Python functionality wouldn't be available. On 15 October 2010 13:04, Kiriakos Vlahos <rep...@bugs.python.org> wrote: > > Kiriakos Vlahos <pyscrip...@gmail.com> added the comment: > > I would like to say that these are two separate issues. One is about the > precision flag and the second about the exception masking flags of the FPU > control words. Both issues affect a wider number of users than Python > embedders using Delphi. For example C# uses 80 bit precision if I > understand http://blogs.msdn.com/b/davidnotario/archive/2005/08/08/449092.aspx well. Technically they are, yes. But they are both affected by any solution that would incorporate preserving or documenting the FPU control word for embedding applications. May be I should have opened a new issue. ---------- nosy: +malkarouri _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9980> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
