Re: [Bug-apl] Something is wrong here (or I may be wrong myself)

2015-04-24 Thread Christian Robert
while this continue to work as designed: D←{24 ⎕cr ⍵} D ∆length ┌2┐ │┌5┐ ┌13───

[Bug-apl] Something is wrong here (or I may be wrong myself)

2015-04-24 Thread Christian Robert
D temp ┌32─┐ │1 0 0 0 0 1 0 0 1 1 0 0 1 1 1 1 0 1 1 0 0 0 0 0 1 0 0 0 0 0 0 0│ └───┘ D bitsidx ┌5─┐ │28 29 30 31 32│ └──┘ bitsidx⊃temp D

Re: [Bug-apl] Not sure

2015-04-24 Thread Blake McBride
Definitely a bug! On Fri, Apr 24, 2015 at 8:14 PM, Christian Robert < christian.rob...@polymtl.ca> wrote: > 132.207.4.11 > 132.207 0.4 0.11 > 24 ⎕cr 132.207.4.11 > ┌3───┐ > │132.207 0.4 0.11│ > └┘ > > > Well, is it a bug or not, I don't know really. Was ty

[Bug-apl] Not sure

2015-04-24 Thread Christian Robert
132.207.4.11 132.207 0.4 0.11 24 ⎕cr 132.207.4.11 ┌3───┐ │132.207 0.4 0.11│ └┘ Well, is it a bug or not, I don't know really. Was typing an IP address. Xtian.

Re: [Bug-apl] using XFRPC11.w3

2015-04-24 Thread Juergen Sauermann
Hi Fausto et al, I believe I have fixed the header problem by relaxing the rules for header variables. Some quick tests with IBM APL2 seem to show that APL2 is very relaxed regarding this. For example you can use the same label twice in a function, or have t

Re: [Bug-apl] using XFRPC11.w3

2015-04-24 Thread Juergen Sauermann
Hi Blake, yes, sorry.  You see that I'm a C++ guy after all :-) . /// Jürgen On 04/24/2015 08:52 PM, Blake McBride wrote: Would't you have to declare it as follows in order for that to work?

Re: [Bug-apl] using XFRPC11.w3

2015-04-24 Thread Blake McBride
And then, of course, do this as line 1: *∆**←**∆1* *Blake McBride* www.arahant.com Cell: 615-394-6760 On Fri, Apr 24, 2015 at 1:52 PM, Blake McBride wrote: > Would't you have to declare it as follows in order for that to work? > > * ∆←∆xl ∆1* > > *Blake McBride* > > www.arahant.com > Cell

Re: [Bug-apl] using XFRPC11.w3

2015-04-24 Thread Blake McBride
Would't you have to declare it as follows in order for that to work? * ∆←∆xl ∆1* *Blake McBride* www.arahant.com Cell: 615-394-6760 On Fri, Apr 24, 2015 at 1:40 PM, Juergen Sauermann < juergen.sauerm...@t-online.de> wrote: > Hi Fausto, > > the *DOMAIN ERROR* is cause by the following func

Re: [Bug-apl] using XFRPC11.w3

2015-04-24 Thread Juergen Sauermann
Hi Fausto, the DOMAIN ERROR is cause by the following function header:  ∆←∆xl ∆ Currently GNU APL rejects function headers with duplicate symbols. IBM APL2 seems to accept duplicate names in the header, but the rules about

Re: [Bug-apl] using XFRPC11.w3

2015-04-24 Thread Kacper Gutowski
On Fri, Apr 24, 2015 at 7:23 PM, Juergen Sauermann wrote: > Now, ATF files are what )IN and )OUT read resp, produce. Chances are that > those > ATF files are the same as for IBM APL2. In that case all you need is to > write them in Dyalog and read them back into GNU APL using command )IN. I remem

Re: [Bug-apl] using XFRPC11.w3

2015-04-24 Thread Fausto Saporito
Hi Jürgen, unfortunately Dyalog supports only extended format (as export format) not ATF... So I need XFRPC workspace to read such format. I found an APLX version of XFRPC, so I read it in APLX then exported in ATF (with )OUT command... APLX supports ATF! YEAH! :) ) But when I try to load the AT

Re: [Bug-apl] using XFRPC11.w3

2015-04-24 Thread Juergen Sauermann
Hi Fausto, maybe you are lucky. The wiki page says:     "2. Using fixed record length ATF files" Now, ATF files are what )IN and )OUT read resp, produce. Chances are that those ATF files are the same as for IBM APL2. In that case all you need is

Re: [Bug-apl] using XFRPC11.w3

2015-04-24 Thread Fausto Saporito
Hello Blake, thanks, maybe this could be useful with Dyalog... regards, Fausto 2015-04-24 18:31 GMT+02:00 Blake McBride : > From years ago, I remember an APL workspace that enabled a standard > interchange format between various APL's. For example, if I remember > correctly, one of the first t

Re: [Bug-apl] using XFRPC11.w3

2015-04-24 Thread Fausto Saporito
Hello Jürgen, thanks for the clarification. I found this page http://aplwiki.com/Transfer%20code and it's talking about APL2000 and others vendors, so I hope to find something similar with GNU-APL and Dyalog. Dyalog supports ]OUT and it generates a XWD file (extended file, not ATF). So I'm wonder

Re: [Bug-apl] using XFRPC11.w3

2015-04-24 Thread Blake McBride
>From years ago, I remember an APL workspace that enabled a standard interchange format between various APL's. For example, if I remember correctly, one of the first things it did was include quad-AV. It then used this to map everything else. I may have a copy of this if anyone is interested. (

Re: [Bug-apl] using XFRPC11.w3

2015-04-24 Thread Juergen Sauermann
Hi Fausto, I believe workspace files are generally not exchangeable between different APL interpreters. In some cases there are commands that allow the exchange of workspaces. For example )IN and )OUT would allow the exchange of workspaces betw

[Bug-apl] using XFRPC11.w3

2015-04-24 Thread Fausto Saporito
Hello all, I'm trying to used the workspace XFRPC11.w3 (downloaded from APL wiki) in order to transfer file from Dyalog APL to GNU-APL. When I try to load XFRPC11 I have an internal error. I suppose the 'w3' format is only for APL2000... correct ? Is there a way to use such method with GNU-APL