Does it mean that scilab no longer carry about interfacing with Fortran (if
ever did it)? Modern Fortran is my prefered language for production codes.

Thanks

2017-03-06 14:28 GMT-03:00 <[email protected]>:

> I had looked up SWIG.  I have found no examples of connecting fortran to
> scilab using swig.
>
> [image: Show details for Clément David ---03/06/2017 03:54:24 AM---> While
> I'm on the subject, the old  Intersci system was a very convenient way to
> automatically > ge]Clément David ---03/06/2017 03:54:24 AM---> While I'm
> on the subject, the old  Intersci system was a very convenient way to
> automatically > ge
> [image: Hide details for Clément David ---03/06/2017 03:54:24 AM---> While
> I'm on the subject, the old  Intersci system was a very convenient way to
> automatically > ge]Clément David ---03/06/2017 03:54:24 AM---> While I'm
> on the subject, the old  Intersci system was a very convenient way to
> automatically > ge
>
> From: Clément David <[email protected]>
> To: Users mailing list for Scilab <[email protected]>
> Cc: [email protected]
> Date: 03/06/2017 03:54 AM
> Subject: using intersci in 6.0.0 (was: Matlab vs Scilab perf; calling a
> fortran routine.)
> ------------------------------
>
>
>
> > While I'm on the subject, the old  Intersci system was a very convenient
> way to automatically
> > generate the interface routine between scilab and an arbitrary fortran
> subroutine.  There seems
> > not to be recent documentation on doing the same (specifically for
> fortran).  Or am I missing
> > something?   I've had to use the "call" interface to use old code.  Is
> there a better way?
>
> In Scilab 6.0.0, we did not reproduce and intersci code generation as this
> is handled by another
> tool called `SWIG` [1] for multiple scripting (or not) languages. This
> idea is to let the tool parse
> an C interface description (similar to a .h file with directives) and
> generate the wrapper code for
> a specific language.
>
> Scilab is natively supported and the tool generates API Scilab code. IMHO
> this is way simpler to
> define in interface just writing C code instead of guessing what's the
> intersci encoding scheme :)
> for a specific parameter.
>
> [1]: http://swig.org/
>
> Thanks,
>
> --
> Clément
>
>
>
> _______________________________________________
> users mailing list
> [email protected]
> http://lists.scilab.org/mailman/listinfo/users
>
>
_______________________________________________
users mailing list
[email protected]
http://lists.scilab.org/mailman/listinfo/users

Reply via email to