I compile Fortran to generate a dll file for VB to call, but there is a problem when compiling, plea

This kind of resource is still searched on or google, if someone has ever published it on the Internet, or there is ****, it will generally be included in the search engine; If you can't find it, you can find a related forum, preferably the kind of forum with a high popularity, register as a member, post for help, and there will be a master to help you.

Do you want to show the Q&A on "Know" on your **? Get it for free**!

If you want to make a complaint or make comments, please go to Know the Complaint Bar for feedback.

Without looking closely, the visual inspection was caused by passing strings.

Try passing in an infile in a vb function, and then passing in an infile with a length, such as 30

VB passed in the dll parameter out of bounds, right, use arrays? The size of the incoming array may not be appropriate, and the array definition is large enough.

It's not accurate. Make it clear.

Is it that the memory in the fortran dll is not freed when it exits??? I don't know.

It's best to be able to paste some of the ** that Song Hu called it.

Yesu

Because it is not clear, the name is not left.

Variables b and d are only used in Fortran and are not Visual Basic, so VB cannot display the value.

Unless you add a function that outputs b and d in Fortran, you can get the result by running the function in VB.

I haven't used fortran, but the principle is pretty much the same).

Addendum: You leave the mailbox, I'll send you the source** over...

I tried, **execution works.

I took a look and it should be in the absence of the arraytest function, I used the Compaq Visual Fortran 6 version, put it! $attributes dllexport ::arraytest

Changed to: !ms$ attributes dllexport::arraytest

This isn't all! The opening statements have been commented out.

A lot of socks to simplicity! The opening statement is used to pass compilation information to the compiler, such as your reputation statement, which tells the editor to compile into a dll file, not a comment statement.

You can press F1 to query under PS.

Another: It is recommended to throw the PS, at least change the CVF or IVF.

After the number, the compiler with some special characters and fewer functions can be used as comments, but the compiler with more functions or advanced points will interpret it as another instruction (similar to define), so it will compile additional functions into it. OpenMP, for example, is a good example of this.

It would be better to translate the Fortran source ** directly into C++. Fortran's process of executing the program is really not complimentary.

Maybe it's a matrix operation, right? The landlord can go back and check.

fortran**.

attributes dllexport::arraytest should be! $dec attributes dllexport ::arraytest

All you need is a dll. lib, exp leave it alone.

If you want to know if the generated dll exports ArrayTest or arraytest@8, use the Dependency Walker to open the DLL.

No, I often use dll for this piece of Sakura, and I didn't find this situation.