Re: [Bug-apl] FILE_IO library

I've fixed the Quad_FX::fun thing as well now. Regards, Elias On 1 August 2014 20:57, Juergen Sauermann wrote: > Hi Elias, > > as far as I can see you use a nested vector of strings as right argument > of ⎕FX. > In that case Str0() is the best way to represent an empty line. > > Another thin

Re: [Bug-apl] FILE_IO library

My mistake. I went back and checked my code; I was passing ⍬ rather than '' for an empty line. I've fixed my code; the package manager will now load APL which has empty lines in function definitions. On Fri, 2014-08-01 at 12:17 +0200, Juergen Sauermann wrote: > Hi, > > do you have an example? Se

Re: [Bug-apl] FILE_IO library

Hi Elias, thanks, included in SVN 411. /// Jürgen On 08/01/2014 03:58 PM, Elias Mårtenson wrote: OK, it's been committed now. Now it's possible to put blank lines in the function editor. Regards, Elias On 1 August 2014 21:15, Elias Mårtenson > wrote: Thank

Re: [Bug-apl] FILE_IO library

OK, it's been committed now. Now it's possible to put blank lines in the function editor. Regards, Elias On 1 August 2014 21:15, Elias Mårtenson wrote: > Thank you. I will implement this shortly. Make sure you update it before > the 1.4 release. > > Regards, > Elias > On 1 Aug 2014 20:57, "Jue

Re: [Bug-apl] FILE_IO library

Thank you. I will implement this shortly. Make sure you update it before the 1.4 release. Regards, Elias On 1 Aug 2014 20:57, "Juergen Sauermann" wrote: > Hi Elias, > > as far as I can see you use a nested vector of strings as right argument > of ⎕FX. > In that case Str0() is the best way to r

Re: [Bug-apl] FILE_IO library

Hi Elias, as far as I can see you use a nested vector of strings as right argument of ⎕FX. In that case Str0() is the best way to represent an empty line. Another thing I saw is that you instantiate a Quad_FX object. That is unnecessary because there is an instance called fun for every syste

Re: [Bug-apl] FILE_IO library

It's changed. You can pull the new version of SQL.apl which now has double-lamps for the docstrings. On 1 August 2014 18:27, Elias Mårtenson wrote: > OK, I'll update the Emacs code to do this. > > Regards, > Elias > > > On 1 August 2014 18:11, Juergen Sauermann > wrote: > >> Hi, >> >> from my

Re: [Bug-apl] FILE_IO library

I just checked my code, and it actually passes empty strings as a one-character string containing a single space instead. I think I did that in order to avoid some problems I had earlier with empty lines. Here's the code that does it: https://github.com/lokedhs/gnu-apl-mode/blob/master/native/DefCo

Re: [Bug-apl] FILE_IO library

OK, I'll update the Emacs code to do this. Regards, Elias On 1 August 2014 18:11, Juergen Sauermann wrote: > Hi, > > from my side - yes. > > /// Jürgen > > > > > On 08/01/2014 12:00 PM, Elias Mårtenson wrote: > > So, should we settle for double ⍝ then? In other words, like this: > > ∇Z←foo X

Re: [Bug-apl] FILE_IO library

Hi, do you have an example? Seems to work outside emacs: * ⎕FX 'FOO' '1' '' '3'** **FOO** ** ⎕CR 'FOO'** **FOO** **1 ** **3 ** * /// Jürgen On 08/01/2014 04:15 AM, Elias Mårtenson wrote: Oh yeah, now that you mention it I remember seeing the same thing. Blank lines gets eaten wh

Re: [Bug-apl] FILE_IO library

Hi, from my side - yes. /// Jürgen On 08/01/2014 12:00 PM, Elias Mårtenson wrote: So, should we settle for double ⍝ then? In other words, like this: ∇Z←foo X ⍝⍝ Doc comment ⍝⍝ This one too ⍝ But not this one Z←X+1 ∇ Regards, Elias On 1 August 2014 17:56, Juergen Sauermann mailto

Re: [Bug-apl] FILE_IO library

So, should we settle for double ⍝ then? In other words, like this: ∇Z←foo X ⍝⍝ Doc comment ⍝⍝ This one too ⍝ But not this one Z←X+1 ∇ Regards, Elias On 1 August 2014 17:56, Juergen Sauermann wrote: > Hi, > > the ⍝⍝ comes from way doxygen works. > > For example, // is a C/C++ comment w

Re: [Bug-apl] FILE_IO library

Hi, the ⍝⍝ comes from way doxygen works. For example, // is a C/C++ comment while /// is a C/C++ comment understood by doxygen. In VHDL, -- is a VHDL comment while --- is a VHDL comment understood by doxygen. etc. I didn't want to go as far as using ⍝⍝⍝ (and no need to since ⍝ alone is a co

Re: [Bug-apl] FILE_IO library

Oh yeah, now that you mention it I remember seeing the same thing. Blank lines gets eaten when the function is defined using ⎕FX. You can see that when using the function editor in the Emacs mode. On 1 August 2014 10:11, David B. Lamkins wrote: > One caution about blank lines: I seem to have tr

Re: [Bug-apl] FILE_IO library

One caution about blank lines: I seem to have tripped on quad-FX choking on empty lines. (This would've been in the case where the argument is a list, not an array.) I haven't checked recently... On Fri, 2014-08-01 at 10:03 +0800, Elias Mårtenson wrote: > I don't really like the cut line. I'd rath

Re: [Bug-apl] FILE_IO library

I don't really like the cut line. I'd rather see the use of a blank line to make this separation if needed: ∇Z←foo X ⍝ Doc comment ⍝ This one too ⍝ But not this one Z←X+1 ∇ Now, in your latest example, you went back to using a single ⍝ character as prefix. This is in line with my current

Re: [Bug-apl] FILE_IO library

On Fri, 2014-08-01 at 00:32 +0800, Elias Mårtenson wrote: > So you are basically suggesting using the same principle as me, just > using two ⍝ symbols instead of one? I'm OK with that. :-) I have a difficult time imagining a use case that'd have two different kinds of comments at the beginning of

Re: [Bug-apl] FILE_IO library

Hi, the whole comment would go into Doxygen as one block. Doxygen has different output formats (HTML, Tex, PDF so HTML markup would not work for the others. But they have their own markup link \b for bold. I downloaded the Doxygen sources. It looks feasible to add a language. Not trivial but

Re: [Bug-apl] FILE_IO library

So you are basically suggesting using the same principle as me, just using two ⍝ symbols instead of one? I'm OK with that. :-) Should be first line be the "summary"? Should we allow leading spaces before the ⍝⍝? Should we assume that the content of the doc comment is HTML or some other kind of ma

Re: [Bug-apl] FILE_IO library

Hi Elias, the standard Doxygen way would be ⍝⍝< I believe. But I doubt that we will get Doxygen support for APL unless we contribute it ourselves (their wishlist is somewhat lengthy and APL is most likely not on their top-10 list). Another way would be to define our own marker and then trans

Re: [Bug-apl] FILE_IO library

Right now, yes. It is the first comment block. If you want to define a more complex format, please go ahead. I'll update the Emacs code to make something clever with it. :-) On 31 July 2014 23:26, Juergen Sauermann wrote: > Hi Elias, > > so its simply an APL comment at the beginning of the fun

Re: [Bug-apl] FILE_IO library

Hi Elias, so its simply an APL comment at the beginning of the function? I would still propose some kind of marker that distinguishes it from normal APL comments (and in order to make it Doxygen compatible). /// Jürgen On 07/31/2014 05:03 PM, Elias Mårtenson wrote: Docstrings is documentati

Re: [Bug-apl] FILE_IO library

Docstrings is documentation for a function, embedded in the function definition itself, as discussed in a previous thread last week or so. Here's an example for the Connect command: https://github.com/lokedhs/apl-sqlite/blob/master/SQL.apl#L20 The Emacs mode uses this to provide integrated docume

Re: [Bug-apl] FILE_IO library

Hi Elias, I changed/removed the _5000 functions as proposed What are docstrings? /// Jürgen On 07/31/2014 09:36 AM, Elias Mårtenson wrote: I checked out the helper library for FILE_IO. Very nice. First of all, how about adding docstrings in the same form as the SQL library? I'm willing to