[Scilab-users] using intersci in 6.0.0 (was: Matlab vs Scilab perf; calling a fortran routine.)

[Adelson Oliveira]

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 <shorne at energetiq.com>:

> 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 <clement.david at scilab-enterprises.com>
> To: Users mailing list for Scilab <users at lists.scilab.org>
> Cc: shorne at energetiq.com
> 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
> users at lists.scilab.org
> http://lists.scilab.org/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.scilab.org/pipermail/users/attachments/20170306/63b8e9b6/attachment.htm>