Dyalog Forums

You might like to use an operator to localise the use of origin 0.

      I0←{⎕IO←0 ⋄ ⍺←⊢ ⋄  ⍺ ⍵⍵ ⍵} 
      ⍳I0 3
0 1 2
      2⊃I0 'abcd'
c

CPU cycles are often cheaper than development time. APL programs are prone to overcompute. q←⍎¨V←40⍴ '2+2' '+/⍳1E7' Let's execute each unique element only once. q≡{(⍎¨⍵)[⍵⍳⍺]}∘∪⍨ V 1 EEN←{(⍎¨⍵)[⍵⍳⍺]}∘∪⍨ ⍝ fn: execute each nub q≡EEN V 1 Execute is one function: an operator would make the technique use ...

A correction: the ⎕R with the wrapp function captures attributes of the P but fails to preserve them. It should of course be:

      wrapp←{'<p',(1 subpat ⍵),'>',NL,(72 8 wrap 2 subpat ⍵),NL,'    </p>'}

Here's a happy thing I stumbled across while cleaning up a thousand HTMs. The HTML is a mashup from multiple sources, including fragments of Word documents pasted in through a WYSIWYG editor. The target is clean structural HTML. Part of the task is to remove empty HTML elements. As the source has ...

Okay, just needs a delay in the loop to allow the OLEClient to subside gracefully.

Function LoadXL from ws loaddata seems to get into a strange state under each . Dyalog APL/W Version 14.0.20815 Serial No : 501502 Unicode Edition Beta release Tue Apr 29 15:57:24 2014 clear ws )copy loaddata LoadXL C:\Program Files\Dyalog\Dyalog APL 14.0 Unicode\ws\loaddata saved Mon Mar 31 17:18 ...

Update: the required ID is found by

      req.GetData 'receiver'

I have multiple drop targets, and need to identify the element that triggered the call to APLJax. It looks as if I should be able to read its ID from declared public field what as illustrated in jqondemo.dyalog. I can certainly read its sibling field event . But trying to read what yields a value ...

Andy, thanks. Using 'Hidden' as below: ⎕CMD 'C:\domything.exe C:\to\this\file.dat' 'Hidden' returns execution immediately to APL, leaving the EXE to run. The CHM says of 'Hidden': Application is run in an invisible window. Might be useful to extend that: Application is run in an invisible window and ...

What's the simplest way to launch a batch job in Windows from Dyalog? That is, execute a Windows shell command that will run to completion without further interaction with the Dyalog task that launched it.

(In APL+Win a left arg to ⎕CMD is all I need for the ⎕CMD to return immediately after launch.)