Re: [f2py] FW: f90 types as modul variables

oh, you are right, this works perfect! :-)

Sorry, i didn't test your first answer, i thought it was one of the ways i have tested yet...
But now, i really know how f2py works. Great!

Thank you very much!
Malte

-----------------------------------------------------------------------------
Deutsches Zentrum für Luft- und Raumfahrt e.V.
in der Helmholtz-Gemeinschaft
Ausbildung - Duale Hochschule Baden-Württemberg

Malte Mauelshagen

Lilienthalplatz 7
38108 Braunschweig
Tel.: 0531/295-2483



-----Original Message-----
From: f2py-users-bounces-Y4l6ocDipWCuvFJfX82//[email protected] on behalf of Pearu Peterson
Sent: Fri 29.01.2010 15:31
To: For users of the f2py program
Subject: Re: [f2py] FW: f90 types as modul variables
 


[email protected] wrote:
> Hi,
> Thank you for your answer. :)
> But this is exactly the way i do NOT want to do it! ;-)
> Since i have the problem with the derived types, i have several files that only should be compiled, but not wrapped.

When you provide .pyf file to `f2py -c` then .f90 files will *not* be
scanned by f2py for wrapping,
all .f90 files will be just compiled and their
object codes will be linked to the extension module.
See also http://cens.ioc.ee/~pearu/papers/IJCSE4.4_Paper_8.pdf

> I don't need acces on the derived types, i just wanna have acces on a subroutine or module that USES object files with derived types.
> Is this possible?

I don't see any problems with that.

Pearu

_______________________________________________
f2py-users mailing list
f2py-users-Y4l6ocDipWCuvFJfX82//[email protected]
http://cens.ioc.ee/mailman/listinfo/f2py-users

_______________________________________________
f2py-users mailing list
f2py-users-Y4l6ocDipWCuvFJfX82//[email protected]
http://cens.ioc.ee/mailman/listinfo/f2py-users