Re: [Bug-apl] Can't )LOAD a dumped file anymore

[Blake McBride]

Dear Juergen,

Thanks.  I will test and let you know.

I was using happily using workspaces until I heard the was movement towards dump files.  At the time, dump files came in handy because I could just edit the .apl in a text editor.  Emacs mode and my own APL function editor (written in APL that I just got working) make dump files pretty much a non-issue for me.  One thing though is code repositories.  Storing text dump files is preferable to (essentially) binary workspaces,

Having said all that, I think I will only use workspaces except for in source code repositories.

Ultimately, I'd love to see )COPY work with dump files (.apl).  For now though, disabling )COPY on .apl files and printing a message is probable best.  Presuming getting )COPY to work on .apl files is a big job, I'd put that on the back burner and focus on the critical functionality issues - which are diminishing fast!

Thanks a lot!

Blake

On Fri, May 30, 2014 at 9:59 AM, Juergen Sauermann <address@hidden> wrote:

Hi Blake,

thanks, fixed it already. But then a svn revert rolled it back.
This issue (and also the #2) should be fixed in SVN 301 but
tests are ongoing.

The only thing left over right now is selective )COPY with .apl files.
I wonder if this is needed or not? I could (1) add a warning that this
is not supported or (2) rework the )COPY command to support it.

(2) would need a parser for .apl files like the one for .xml files.
That takes a while because right now .apl files are simply executed
with no mechanism to skip functions or variables.

/// Jürgen

On 05/30/2014 04:30 PM, Blake McBride wrote:

Greetings,

With the ;latest update (300), I can no longer )LOAD a )DUMP'ed file:

      )LOAD KeyedFiles

loading )DUMP file /home/blake/workspaces/KeyedFiles.apl...

WAS CLEAR WS

==============================================================================

Assertion failed: lines.size() > 0

in Function:      execute_edit

in file:          Nabla.cc:696

Call stack:

----------------------------------------

-- Stack trace at Nabla.cc:696

----------------------------------------

0x7f547844ade5 __libc_start_main

0x435e85  main

0x52ffed   Workspace::immediate_execution(bool)

0x4660bd    Command::process_line()

0x464de5     Command::process_line(UCS_string&)

0x4854c4      Nabla::edit_function(UCS_string const&)

0x485108       Nabla::edit()

0x4842bd        Nabla::execute_edit()

0x44416f         do_Assert(char const*, char const*, char const*, int)

========================================

And the error go on and on.

Thanks.

Blake