forums.silverfrost.com

I was wondering if there has been any progress in this? Has anyone used parallelisation successfully in ftn95?

So basically in the new version of ftn95 (but not the current 8.83) we will be able to use the command !ftn95$OPTIONS(-UNDEF) at the beginning of a file, correct?

!ftn95$OPTIONS(-UNDEF)
used to work in 8.72, it now fails in 8.82 and 8.83.
I have to say that in the last version where it worked, it was not possible to do
!ftn95$OPTIONS(UNDEF)
later on f ...

So what is the conclusion from this thread? Is it an ftn95 bug (zeroing not happening properly) or is it a user error?
I am asking because I occasionally get the same error (cannot easily repeat it).

Courtesy of https://stackoverflow.com/questions/19147743/passing-allocatable-array-from-fortran-to-c-and-malloc-it

#include "stdlib.h"
int *create_storage()
{
/* Arra ...

We just want to develop our own malloc/free Fortran calls, and iso_c_binding allows to use the C pointers seamlessly. In any case C_F_POINTER is a very important element of iso_c_binding so it is impo ...

Sorry, somehow didn't get a notification of your reply.
The code is the one in the accepted answer
https://stackoverflow.com/questions/19147743/passing-allocatable-array-from-fortran-to-c-and-malloc ...

Is this implemented fully?

For example C_F_POINTER doesn't seem to be recognised.

Indeed, you are right, there is a "stack" command for slink64, but for some reason in our scripts the following line
stack 30000000
causes the program to show the following error

The sy ...

We are having the same issue now that we use the same script files for 32bit and 64bit.
Is there a way for slink64 to know that a line with
stack
is only for 32bit?

I am sure there are many programs written in python or php for these (just google for github trading algorithms). The problem with stop loss order is that you have fees to pay all the time, so if the ...

Just wanted to add that I too have noticed this bug when running with undef.

This only happens with the full code, not with a simple example, but nevertheless I am showing it here in case you see anything that may explain it.
The error is

Attempt to call a routine with si ...

Thanks Paul - by the way I haven't received anything in my Messages inbox yet.

Yes indeed. I have now cleared *all* duplicate salflib* etc. dlls !