Menu ▾ ▴

#100 Add support for procedures saving and restoring

closed
nobody
None
5
2018-04-09
2011-04-11
No

The current implementation of SAVE and RESTORE procedures supports only variables saving. I would like to save also procedures that are loaded in memory and not just variables. IDL does it and it would be nice to see it working in GDL too.

Discussion

  • Sylwester Arabas

    Hello, could you provide any reason for having this feature in a free/open-surce version of IDL? (compatibility with IDL would not be achieved anyhow)

    Best,
    Sylwester

     
  • Fernando Silveira

    The first reason I'd like to have procedures saving/restoring is that it takes more than 10 minutes to compile all the software I have in one of my systems. By restoring it from an already compiled file I think that it could be reduced to some mere seconds, just like IDL. My software runs dozens of CPUs at the same time.

    The second thing is that it is much easier to handle and distribute the procedures I write in one compiled binary file than lots of .pro file. This is not the biggest issue but it would help the users very much.

    Cheers,
    -Fernando

     
  • Erik Bergbäck Knudsen

    Bump on that - I would also like to see this. Some third party scientific applications are only distributed as a binary "bunch" of procedures. I realize that I could just run this under IDL, but I'd very much prefer an open source option.

     
  • Sylwester Arabas

    Just for the record, this was one of the topics discussed during the GDL workshop in Paris last year.

    Since binary compatibility with IDL is not attainable by design, the major reason is the speedup. This would be a similar mechanism as the one in Python that produces .pyc files.

    During the discussion, we noted that it would be needed to serialise the ProgNode instances into the save files.

     
  • Sylwester Arabas

    • status: open --> closed
    • Group: --> Next Release (example)
     

Log in to post a comment.