Fault in version 18.0.38756

No need to worry about going "off topic" here
Forum rules
This forum is for general chit-chat, not necessarily APL-related. However, it's not for spam or for offensive or illegal comments.
Post Reply
User avatar
jmosk
Posts: 69
Joined: Thu Jul 18, 2013 5:15 am

Fault in version 18.0.38756

Post by jmosk »

I have been using v18.0 for a long while. I have now had two occurrences where a program I was running went into an infinite loop (for some unknown reason) and the Action/Interrupt would not abort the execution. I do not know why this may have occurred. But I had no choice but to exit Dyalog and unfortunately both times I had forgotten to save extensive updates and lost all of them.

Has this issue been reported before? What is the latest version I should update to?
+←--------------------------------------------------------------→
+ Jay Moskowitz
+←--------------------------------------------------------------→
+ http://www.linkedin.com/in/jay-moskowitz-5745b83
+
RichardP|Dyalog
Posts: 33
Joined: Fri Oct 12, 2018 3:05 pm

Re: Fault in version 18.0.38756

Post by RichardP|Dyalog »

Unfortunately without more details, it is impossible to say why this is happening or what to do to mitigate it.

I recommend you use Link to keep your active workspace synchronised with a folder on the file system - that way, whenever you make changes to something in the workspace then those changes are reflected in source code in text files.

It is typical to create a link between the root namespace # and some folder when experimenting or working on an isolated project.

Code: Select all

]Create # /path/to/my-project-folder
You make changes using the editor either by closing the editor (Esc key or the "X" in the top-left) or using the FX keyboard shortcut which can be set by going to Options → Configure → Keyboard Shortcuts in the Windows IDE or Edit → Preferences → Shortcuts in RIDE.

See the Link User Guide for more information https://dyalog.github.io/link/
Vince|Dyalog
Posts: 439
Joined: Wed Oct 01, 2008 9:39 am

Re: Fault in version 18.0.38756

Post by Vince|Dyalog »

Hi Jmosk,

As well as using Link, I have another recommendation.

You should not be using Dyalog 18.0.38756. It is almost 4 years old and is missing 4 years of fixes.

We would recommend 18.2. It is available in our Download zone. I will write an email to you from Support.

Regards,

Vince
User avatar
jmosk
Posts: 69
Joined: Thu Jul 18, 2013 5:15 am

Re: Fault in version 18.0.38756

Post by jmosk »

Yes, I will upgrade to V18.2.

Never knew about Link. That is a great feature to provide peace of mind. I am always worried that if my workspace .dws file is corrupted I have lost tons of work and would have to retype written copies of code. It is nice to see an automatic text backup copy of my code being saved for me automatically.
+←--------------------------------------------------------------→
+ Jay Moskowitz
+←--------------------------------------------------------------→
+ http://www.linkedin.com/in/jay-moskowitz-5745b83
+
User avatar
jmosk
Posts: 69
Joined: Thu Jul 18, 2013 5:15 am

Re: Fault in version 18.0.38756

Post by jmosk »

I tried ]Link and it created a link between my active directory and a backup folder I created. But when doing )ed myProgram, changing some lines, and exiting, I did not see a file created in that folder. Do I need to do something else?

Also, the command ]Link List or ]Link -List, did not return the name of the linkage I created which was confirmed when I created it. It returned:

* Ambiguous user command; to see a list of all valid user commands that start with "link", type
]link* -?

It is running version 2.0.3 of Link.
+←--------------------------------------------------------------→
+ Jay Moskowitz
+←--------------------------------------------------------------→
+ http://www.linkedin.com/in/jay-moskowitz-5745b83
+
Vince|Dyalog
Posts: 439
Joined: Wed Oct 01, 2008 9:39 am

Re: Fault in version 18.0.38756

Post by Vince|Dyalog »

Hi Jay,

I don't think that there is a ]link.list command.

There is a .status command you can try:
]link.status

With 18.2, I think you should be using Link 3.0, so I will write to you about that from Support.

Regards,

Vince
Post Reply