matplotlib-devel Mailing List for matplotlib

John Hunter wrote:
> On 7/13/07, Eric Firing <ef...@ha...> wrote:
> 
>> No, it is not your installation. You have identified an area that needs
>> work, after we settle on a possibly new import and namespace strategy.
> 
> This is definitely something new -- help(pylab) used to display the
> rather extensive pylab doc string, which starts with in pylab.py:
> 
> ""
> This is a matlab(TM) style interface to matplotlib.
> 
> The following plotting commands are provided; some of these do not
> exist in matlab(TM) but have proven themselves to be useful
> nonetheless.
> The majority of them, however, have matlab analogs
> ...snip
> """
> 
> Are eggs doing something fishy here? This is a weird one.
> JDH
But it does it on linux, not using eggs. I couldn't figure it out--just 
 assumed it had always done that, and I had never noticed.
Still, the matplotlib/__init__.py docstring could be changed to make 
clear the distinction between mpl and the pylab interface. Instead, it 
talks only about the latter:
efiring@manini:~/programs/py/mpl/matplotlib_units/lib/matplotlib$ head 
__init__.py
"""
This is a matlab(TM) style functional interface the matplotlib.
The following matlab(TM) compatible commands are provided by
 >>> from pylab import *
Plotting commands
 axes - Create a new axes
Eric

On 7/13/07, Eric Firing <ef...@ha...> wrote:
> No, it is not your installation. You have identified an area that needs
> work, after we settle on a possibly new import and namespace strategy.
This is definitely something new -- help(pylab) used to display the
rather extensive pylab doc string, which starts with in pylab.py:
""
This is a matlab(TM) style interface to matplotlib.
The following plotting commands are provided; some of these do not
exist in matlab(TM) but have proven themselves to be useful
nonetheless.
The majority of them, however, have matlab analogs
...snip
"""
Are eggs doing something fishy here? This is a weird one.
JDH

OK, I reverted back to the tried and true MPL way... It hasn't been 
completely unproductive, however: I added tests for infinity (either 
sign) and finite-ness to MPL_isnan.h. (On top of which I now understand 
the IEEE 754 representations far better than I care to.)
Now, this should work just like it did in the good old days... I mean it 
this time. :)
John, commence using your infinity-finding powers!
-Andrew

Can you stick this in the top of src/_transforms.cpp and see if you
still get the problem?
#define _GLIBCPP_USE_C99
-Andrew
John Hunter wrote:
> On 7/13/07, Andrew Straw <str...@as...> wrote:
>> I think I figured out and fixed the situation with isnan.
>>
>> >From http://lists.apple.com/archives/xcode-users/2005/Feb/msg00196.html
>>
>>> Basically the story is this:
>>> isnan() is a C99 extension to standard C.
>>> Standard C++ is based on an older standard of C.
>>> Hence isnan() is not part of standard C++ and may or may not work.
>> But std::isnan() is part of standard C++ defined in <cmath>.
>>
>> Since we use C++ (which numpy doesn't) we can drop our own isnan support
>> and use std::isnan(). Which I just did.
> 
> We're not out of the woods yet. On my OS X 10.3 powerbook
> 
> src/transforms.cpp: In member function `Py::Object Bbox::update(const
> Py::Tuple&)':
> src/transforms.cpp:476: error: `isnan' undeclared in namespace `std'
> src/transforms.cpp:476: error: `isnan' undeclared in namespace `std'
> 
> John-Hunters-Computer:~/mpl> gcc --version
> gcc (GCC) 3.3 20030304 (Apple Computer, Inc. build 1495)
> 
> JDH
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

On 7/13/07, Andrew Straw <str...@as...> wrote:
> I think I figured out and fixed the situation with isnan.
>
> >From http://lists.apple.com/archives/xcode-users/2005/Feb/msg00196.html
>
> >
> > Basically the story is this:
> > isnan() is a C99 extension to standard C.
> > Standard C++ is based on an older standard of C.
> > Hence isnan() is not part of standard C++ and may or may not work.
>
> But std::isnan() is part of standard C++ defined in <cmath>.
>
> Since we use C++ (which numpy doesn't) we can drop our own isnan support
> and use std::isnan(). Which I just did.
We're not out of the woods yet. On my OS X 10.3 powerbook
src/transforms.cpp: In member function `Py::Object Bbox::update(const
 Py::Tuple&)':
src/transforms.cpp:476: error: `isnan' undeclared in namespace `std'
src/transforms.cpp:476: error: `isnan' undeclared in namespace `std'
John-Hunters-Computer:~/mpl> gcc --version
gcc (GCC) 3.3 20030304 (Apple Computer, Inc. build 1495)
JDH