Re: Python/Fortran interoperability

In article , sturlamolden wrote: > >You also made this claim regarding Fortran's C interop with strings: > >"No, I mean things like 'Kilroy was here'. Currently, Fortran's C >interoperability supports only strings of length 1, and you have >to kludge them up as arrays. That doesn't work very we

Re: Python/Fortran interoperability

In article <1032c78d-d4dd-41c0-a877-b85ca000d...@g31g2000yqc.googlegroups.com>, sturlamolden wrote: >On 23 Aug, 12:35, n...@cam.ac.uk wrote: > >> I am interested in surveying people who want to interoperate between >> Fortran and Python to find out what they would like to be able to do >> more co

Python/Fortran interoperability

I am interested in surveying people who want to interoperate between Fortran and Python to find out what they would like to be able to do more conveniently, especially with regard to types not supported for C interoperability by the current Fortran standard. Any suggestions as to other ways that

Re: Python/Fortran interoperability

In article , glen herrmannsfeldt wrote: > >< Consider, for example: > > > >< This is not currently allowed and r

Re: Python/Fortran interoperability

In article <7abee4bb-b18a-4680-817b-7e76aed40...@c2g2000yqi.googlegroups.com>, sturlamolden wrote: > >> Precisely. =A0And the kludge does NOT work under all circumstances, >> which is why I said that it doesn't work very well. > >Do you have an example? I gave you one. Also see below. >> Consi

Re: Python/Fortran interoperability

In article <1j4y84p.v5docbtueccmn%nos...@see.signature>, Richard Maine wrote: > >Only character strings of length 1 are interoperable, as the term >"interoperable" is defined in the Fortran standard. However, that does >not mean that only character strings of length 1 will work with C. The >distin

Re: Python/Fortran interoperability

In article <5134d9f1-0e23-4e05-a817-bf0cc9e85...@w6g2000yqw.googlegroups.com>, sturlamolden wrote: >On 24 Aug, 02:26, nos...@see.signature (Richard Maine) wrote: > >> You missed the word "OOP", which seemed like the whole point. Not that >> the particular word is used in the Fortran standard, but

Re: Python/Fortran interoperability

In article , JB wrote: >["Followup-To:" header set to comp.lang.fortran.] Sorry - set back again, because you don't provide an Email address, and there's a significant issue. Thanks for the response. >> 1) Do you want to use character strings of arbitrary length? > >As in, a signed C int (