Re: [Bug-apl] FIO[57]

art/encrypted; protocol="application/pgp-encrypted"; boundary=fi9ClwaDJCZaJYRZymFkCCx29801HL9f9 Subject: Re: [Bug-apl] FIO[57] X-BeenThere: bug-apl@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Bugs and suggestions for GNU APL List-Unsubscribe: <https://lists.gnu.org/mailman/options/

Re: [Bug-apl] FIO[57]

just to add to the current confusion - i never got an email sent by you at 6:55AM On Wed, 25 Jul 2018 20:03:23 +0200 Juergen Sauermann wrote: > Hi Blake, > > interesting. From what I can see the only relevant email (the last version > having subject >  Quad-FIO[57] Take 3 has made it to bug-

Re: [Bug-apl] FIO[57]

On Wed, Jul 25, 2018 at 08:03:23PM +0200, Juergen Sauermann wrote: > The Time below (Wed, Jul 25, 2018 at 11:55 AM) does not match any email that I > have sent > (the only outgoing email today was at 6:55 to enztec, responding to his email. That's the mail. 6:55 PM CEST (+0200) in Europe is 11:55

Re: [Bug-apl] FIO[57]

Hi Blake, interesting. From what I can see the only relevant email (the last version having subject  Quad-FIO[57] Take 3 has made it to bug-apl without encryption. The Time below (Wed, Jul 25, 2018 at 11:55 AM) does not match any email that

Re: [Bug-apl] FIO[57]

All we're getting is an empty email with two attachments: noname & encrypted.asc On Wed, Jul 25, 2018 at 11:55 AM Juergen Sauermann < juergen.sauerm...@t-online.de> wrote: >

Re: [Bug-apl] FIO[57]

binianRHZN5rO.bin Description: PGP/MIME version identification encrypted.asc Description: OpenPGP encrypted message

Re: [Bug-apl] FIO[57]

you must be unintentionally checking the pgp/sign/encrypt box somewhere I use sylpheed as my email client? - and the check box can get too easily 'clicked' on by the mouse as it goes over it on it's way to click 'send' but now that i have the real text of the message my apl program to decrypt

Re: [Bug-apl] FIO[57]

Hi, to be honest, I have no idea what's happening. I am sending emails like always, but somehow they seem to become corrupted somewhere. I've sent the FIO[57] email again, hoping it makes it this time. /// Jürgen On 07/24/2018 10:43 PM, Peter Teeson wrote: > I have received 2 of this type of e

Re: [Bug-apl] FIO[57]

I have received 2 of this type of email. I don’t understand why. respect… Peter > On Jul 24, 2018, at 3:38 PM, Juergen Sauermann > wrote: > >

[Bug-apl] FIO[57]

binuuE2Puesp6.bin Description: PGP/MIME version identification encrypted.asc Description: OpenPGP encrypted message

Re: [Bug-apl] ⎕FIO[49]

Very nice. Thanks! Would it make sense to add a tokenisation function as well that one could use as a RO for this operator? Regards, Elias On 27 Jan 2017 23:04, "Juergen Sauermann" wrote: > Hi, > > I have added two wrapper functions in the *FILE_IO* workspace: > > *Z←FIO∆readlines Bs* > > read

Re: [Bug-apl] ⎕FIO[49]

Hi, I have added two wrapper functions in the FILE_IO workspace: Z←FIO∆readlines Bs reads the entire file named Bs (i.e. not a file handle Bh!) line by line and stores each line i in Z[i]. Z←(LO FIO∆transform_lines

Re: [Bug-apl] ⎕FIO[49]

Hi currently we have 'readlines' in the wrapper function FIO which is contained in the FILE_IO workspace. BTW the FILE_IO workspace, already contains this wrapper function Z←L FIO[X] R, kindly provided by Christian Robert, which calls

Re: [Bug-apl] ⎕FIO[49]

Just FYI, it's similar to Dyalog's ⎕NGET . (I'm not suggesting NGET is necessarily a good name to use in wslib5.) On 27 January 2017 at 02:03, Elias Mårtenson wrote: > Speaking of which, ⎕FIO[49] needs a name in wslib5. Any

Re: [Bug-apl] ⎕FIO[49]

Thank you Jürgen. You make a compelling argument. In particular, I'd argue that the ⎕FIO[n] functions should be seen as an internal implementation detail, and the “official” API as it were, should be the wrapper functions. Speaking of which, ⎕FIO[49] needs a name in wslib5. Any suggestions? Rega

Re: [Bug-apl] ⎕FIO[49]

Hi, there is nothing wrong with ⎕ReadLines as such. However, - if I remember correctly then in the 70s APL was very much loved by programmers that were not speaking English every day, in particular in France and Canada. - Eve

Re: [Bug-apl] ⎕FIO[49]

On 25 January 2017 at 05:54, Elias Mårtenson wrote: > Is there anything inherently wrong with having more quad-commands? What is > the reason we have to do ⎕FIO[49] instead of simply ⎕ReadLines or something > like that? > > It's like we're going out of way to make code unreadable. I know APL is all

Re: [Bug-apl] ⎕FIO[49]

I agree 100% with you, read the thread about ⎕FIO['SomeFunctionName'] to be able to use a string as function name, that every one on this planet disagreed with me. a ⎕name for each actual ⎕fio would be fine with me. (in fact, I want to call them by names for years, and not by number) lets all

Re: [Bug-apl] ⎕FIO[49]

Is there anything inherently wrong with having more quad-commands? What is the reason we have to do ⎕FIO[49] instead of simply ⎕ReadLines or something like that? It's like we're going out of way to make code unreadable. I know APL is all about terseness, but I think this is going too far. Am I alo

Re: [Bug-apl] ⎕FIO[49]

In fact we should make all/most ⎕FIO[] in into parantheses things like this was working fine before ⎕FIO[49] fd← "r" ⎕fio[3] ".bashrc" fd 5 ⊣ ⎕fio[4] fd DOMAIN ERROR ⊣⎕FIO[4]fd ^ ^ well, I know now that I have to make it: ⊣ (⎕fio[4] fd) but it's a cha

Re: [Bug-apl] ⎕FIO[49]

Hi Xtian, yes, one thing that I overlooked was that you should put ⎕FIO[49] into parantheses because otherwise it will grab the function left of it and apply it to each line read from the file and not to the final result:   ⎕FIO[49]'x

Re: [Bug-apl] ⎕FIO[49] introduced a complete change of other ⎕FIO[] syntax

LoadSudoku←{{⊂9 9 ⍴¯1+'0123456789' ⍳ ⍵}⎕FIO[49] ⍵} LoadSudoku2←{{⊂9 9 ⍴ ⍵}⍤1 ⊃ ⊢⎕FIO[49] ⍵} LoadSudoku3←{{⊂9 9 ⍴ ⍵} ⎕FIO[49] ⍵} LoadSudoku4←{{⊂9 9 ⍴ ⍵}¨ ⊢ ⎕FIO[49] ⍵} time 'a←LoadSudoku3 "Sudoku_dump.txt"' 12.5218593 time 'a←LoadSudoku3 "Sudoku_dump.txt"' 12.0

[Bug-apl] ⎕FIO[49] introduced a complete change of other ⎕FIO[] syntax

⊣⎕FIO[4]fd DOMAIN ERROR ⊣⎕FIO[4]fd ^ ^ fd 6 ⊣ ⊢⎕FIO[4]fd DOMAIN ERROR ⊣⊢⎕FIO[4]fd ^ ^ ⎕FIO[4]fd 0 how do I silence the result of ⎕FIO[4] ? Xtian.

Re: [Bug-apl] ⎕FIO[49]

Juergen, Just a note, your example as of yesterday to disclose the result of ⎕FIO[49] to obtain a matrix no longer work as is. I had to add a tack (⊢) between ⎕FIO[49] and the "⊃" as in LoadSudoku2 below. LoadSudoku2←{{⊂9 9 ⍴ ⍵}⍤1 ⊃ ⊢⎕FIO[49] ⍵} LoadSudoku3←{{⊂9 9 ⍴ ⍵} ⎕FIO[49] ⍵} witho

[Bug-apl] ⎕FIO[49]

Hi, I have added ⎕FIO[49] to GNU APL in SVN 858. Z←⎕FIO[49] 'filename' reads the file named filename line by line and stores every line of the file in one enclosed item of result vector Z , for example (file x has 3 lines):

Re: [Bug-apl] ⎕FIO[1] behavior

Thank you. On Sat, Dec 24, 2016 at 05:25:54PM +0100, Juergen Sauermann wrote: > Hi David, > > thanks, fixed in SVN 827. > > I believe the reason was that some ⎕FIO functions return valid positive > integers but can also > fail (with an also positive errno). To distinguish between errrors and int

Re: [Bug-apl] ⎕FIO[1] behavior

Hi David, thanks, fixed in SVN 827. I believe the reason was that some ⎕FIO functions return valid positive integers but can also fail (with an also positive errno). To distinguish between errrors and integer results I made all errors neg

[Bug-apl] ⎕FIO[1] behavior

I think that the behavior of ⎕fio[1] changed at some point. This is supposed to return the value of errno (a positive value), but now returns -errno, causing ⎕fio[2] ⎕fio[1] ⍬ to always return "Unknown error ...".

[Bug-apl] ⎕FIO[48]

Hi, I have added a fscanf() function to ⎕FIO as proposed earlier. SVN 772. It can be accessed as ⎕FIO[48] or as FIO∆fscanf after )COPY 5 FILE_IO See the wslib5/FILE_IO.apl workspace or the src/testcases/Quad_FIO.tc testcase file

Re: [Bug-apl] ⎕fio[26] bug when called with a directory name.

Hi Xtian, thanks, fixed in SVN 752. /// Jürgen On 06/23/2016 06:17 AM, Christian Robert wrote:   )save 2016-06-23  00:09:01 (GMT-4) fio   df   fio  ╔══╗    

[Bug-apl] ⎕fio[26] bug when called with a directory name.

)save 2016-06-23 00:09:01 (GMT-4) fio df fio ╔══╗ ║fio ║ ║'' ⎕fio ''║ ╚══╝ errno ╔╗ ║z←errno ║ ║z←⎕fio[1] ''║ ╚╝ getcwd ╔═╗ ║z←getcwd ║ ║z←⎕fio 30║

Re: [Bug-apl] ⎕fio

right ! It was late ... On 2016-03-05 08:14, Kacper Gutowski wrote: On Sat, Mar 5, 2016 at 6:45 AM, Christian Robert wrote: [0] z←Execute cmd;⎕io;fh [7] Fini: ⎕FIO[25] fh [8] ⊃⊃z (...) I do not understand why it repeat the result twice. one via stdout and one via boxing as I can guess.

Re: [Bug-apl] ⎕fio

On Sat, Mar 5, 2016 at 6:45 AM, Christian Robert wrote: > [0] z←Execute cmd;⎕io;fh > [7] Fini: ⎕FIO[25] fh > [8] ⊃⊃z (...) > I do not understand why it repeat the result twice. one via stdout and one > via boxing as I can guess. The function returns z as indicated in its header, but before d

[Bug-apl] ⎕fio

∇Execute[⎕]∇ ∇ [0] z←Execute cmd;⎕io;fh [1] ⎕io←0 [2] fh ← ⎕FIO[24] cmd [3] z←⎕av[⎕fio [8] fh] [4] Loop: →(0≠⎕FIO[10] fh)/Fini [5] z←z,⎕av[⎕fio [8] fh] [6] →Loop [7] Fini: ⎕FIO[25] fh [8] ⊃⊃z ∇ )save 2016-03-05 00:20:57 (GMT-5) CONTINUE D Execute 'date'

Re: [Bug-apl] ⎕FIO

I like. Thanks! Blake On Thu, Jan 28, 2016 at 6:22 AM, Juergen Sauermann < juergen.sauerm...@t-online.de> wrote: > Hello, > > due to the problems with building DLLs under Windows, I have converted the > native function *FILE_IO *of *GNU APL* into a new system function *⎕FIO*. > > *⎕FIO* is use

[Bug-apl] ⎕FIO

Hello, due to the problems with building DLLs under Windows, I have converted the native function FILE_IO of GNU APL into  a new system function ⎕FIO. ⎕FIO is used exactly like FILE_IO, except that it cannot (and does not have to) be ⎕SVO