Re: strange arguments passing problem (from vba to fortran dll)
- From: Brooks Moses <bmoses-nospam@xxxxxxxxxxxxxxxxxx>
- Date: Wed, 30 May 2007 01:40:12 -0700
Arjen Markus wrote:
On 30 mei, 06:03, Brooks Moses <bmoses-nos...@xxxxxxxxxxxxxxxxxx>
wrote:
and that if you only do
Dim control(7), ma(100) As Long
then ma gets defined properly, but control gets typed as whatever VBA's
implicit typing is ("variant", I think).
Oh, a type "variant" would be a very bad idea!
It is a "polymorphic" type that only VB can handle properly -
a bit like array descriptors for assumed-shape arrays:
you can not (easily/portably) pass these to, say, C.
Quite likely that that is the problem.
They can lead to other problems, too....
http://worsethanfailure.com/Articles/My-Friends-Just-Call-Me-Error.aspx
- Brooks
--
The "bmoses-nospam" address is valid; no unmunging needed.
.
- References:
- strange arguments passing problem (from vba to fortran dll)
- From: formulae translator
- Re: strange arguments passing problem (from vba to fortran dll)
- From: Arjen Markus
- Re: strange arguments passing problem (from vba to fortran dll)
- From: formulae translator
- Re: strange arguments passing problem (from vba to fortran dll)
- From: Louis Krupp
- Re: strange arguments passing problem (from vba to fortran dll)
- From: formulae translator
- Re: strange arguments passing problem (from vba to fortran dll)
- From: Brooks Moses
- Re: strange arguments passing problem (from vba to fortran dll)
- From: Arjen Markus
- strange arguments passing problem (from vba to fortran dll)
- Prev by Date: Re: strange arguments passing problem (from vba to fortran dll)
- Next by Date: Re: F77 & WIN XP
- Previous by thread: Re: strange arguments passing problem (from vba to fortran dll)
- Next by thread: Re: strange arguments passing problem (from vba to fortran dll)
- Index(es):