Hi,
I was wondering why the linking was done with g++ with mingw in
numpy.distutils ? (I got some trouble because some function in math
library are only defined for gcc and not g++, for example atanhf). This
also means that g++ is required to build numpy, which is a bit strange
since there
I'm pleased to announce the release of NumPy 1.0.4.
NumPy is the fundamental package needed for scientific computing with
Python. It contains:
* a powerful N-dimensional array object
* sophisticated (broadcasting) functions
* basic linear algebra functions
* basic Fourier transfo
Here's a simple example to document my problem:
!!!
types.f90 !!!
!
module types
integer, parameter :: WP=4, intdim=selected_int_kind(8)
end module types
! end types.f90
!
Hi,
I have one short question, a possible bug report, and one longer question:
1. (short question)
Which mailing list is appropriate for f2py discussion:
numpy-discussion or f2py-users?
2. (bug report?)
I'm using numpy from svn (revision 4410). When using f2py to compile,
I got an error:
File
On Nov 7, 2007 10:35 AM, Sebastian Haase <[EMAIL PROTECTED]> wrote:
> On Nov 7, 2007 5:23 PM, Matthieu Brucher <[EMAIL PROTECTED]>
> wrote:
> >
> > > I don't understand. I'm thinking of most math functions in the
> > > C-library. In C a boolean is just an integer of 0 or 1 (quasi, by
> > > defini
On Nov 7, 2007 5:23 PM, Matthieu Brucher <[EMAIL PROTECTED]> wrote:
>
> > I don't understand. I'm thinking of most math functions in the
> > C-library. In C a boolean is just an integer of 0 or 1 (quasi, by
> > definition).
> >
> > Could you explain what you mean ?
> >
>
> In C++, bool is a new ty
>
> I don't understand. I'm thinking of most math functions in the
> C-library. In C a boolean is just an integer of 0 or 1 (quasi, by
> definition).
>
> Could you explain what you mean ?
>
In C++, bool is a new type that has two values, true and false. If you add
true and true, it is still true,
On Nov 7, 2007 4:45 PM, Matthieu Brucher <[EMAIL PROTECTED]> wrote:
> Unfortunately, operations on boolean are not the same as operations on
> integers, so you can't replace one with another.
I don't understand. I'm thinking of most math functions in the
C-library. In C a boolean is just an integ
Unfortunately, operations on boolean are not the same as operations on
integers, so you can't replace one with another.
Matthieu
2007/11/7, Sebastian Haase <[EMAIL PROTECTED]>:
>
> O.K., so sizeof(bool) is 1.
> But I already have a function instantiation for uint8.
>
> The problem is that without
O.K., so sizeof(bool) is 1.
But I already have a function instantiation for uint8.
The problem is that without doing "some magic" the compiler (?, or
numpy ?) would never allow to use anything but a "dedicated"
bool-typed function for bool.
Even though the CPU treats bool exactly like an integer o
Hi,
I have just finished to implement everything I wanted to do for a
2nd alpha for numpy.scons. Most of the work since 1st alpha was
infrastructure polishing (performance library, fortran): now, most
common performance libraries are fully supported (MKL and ATLAS on
linux, sunperf on sola
Hi,
No, a bool is not an int32. Try just sizeof(bool) to be sure (on my box,
it's one).
Besides, if you use a std::vector of bool, be aware of the fact that it is
not like the other vectors.
Matthieu
2007/11/7, Sebastian Haase <[EMAIL PROTECTED]>:
>
> Hi,
> I have a templated function written in
Hi,
I have a templated function written in C++.
My SWIG typemap instantiates this for many argument array types (such
as unit8, int16, uint16, int32, float32,float64,...)
All works well, except when feeding in a boolean array as in
seb.mmms(a>6)
I get this error:
NotImplementedError: No matching fu
13 matches
Mail list logo
