Hi Elias,
this is actually a consequence of the APL formatting rules which
have no space between adjacent characters:
'f' 'a' 1
fa 1
4 ⎕CR 'f' 'a' 1
┏→━━━┓
┃fa 1┃
┗┛
I noticed the following:
* 'f','a',1*
┏→━━━┓
┃'f''a' 1┃
┗┛
Is this intentional, or is there a missing space between 'a' and 'a'?
Regards,
Elias
On 17 April 2016 at 00:26, Juergen Sauermann
wrote:
> Hi Elias,
>
> that wasn't required was it :-) ? *SVN 721*.
>
> /// Jürgen
>
>
Hi Elias,
that wasn't required was it
:-) ? SVN 721.
/// Jürgen
On 04/16/2016 06:01 PM, Elias Mårtenson
wrote:
One bug though: I'm not able to specify 29 as a
parameter to ]BOXING.
One bug though: I'm not able to specify 29 as a parameter to ]BOXING.
Regards,
Elias
On 16 April 2016 at 23:55, Elias Mårtenson wrote:
> Very nice! It's so much better, that I have to create an example showing
> just how neat it is.
>
> Here's the result from selecting from a simple table using
Very nice! It's so much better, that I have to create an example showing
just how neat it is.
Here's the result from selecting from a simple table using 8⎕CR:
* 8⎕CR 'select * from foo' SQL∆Select[db] ⍬*
┌→─┐
↓ 1 ┌→──┐┌→──┐ 832│
│ │foo││Valu
Hi Elias, Blake,
I have added 29 ⎕CR in SVN 720.
It uses e.g. 'a'
for character scalars, "hello" for character strings,
and a double-line frame around character arrays with higher ranks.
29 ⎕CR 2 3⍴
1 2.2 'a' "hel
Putting quotes around strings is important so you can see leading and
trailing blanks.
On Wed, Apr 13, 2016 at 1:07 PM, Juergen Sauermann <
juergen.sauerm...@t-online.de> wrote:
> Hi,
>
> I can look into this. However, how shall we handle character arrays with
> rank > 1?
> Quotes on every line o
Hi,
this looks more like a comma separated value list ( fds ⎕CSV Array )
fds: field delimiter string like
fds←' ",;≡'
fds[1] ←→ Numeric field quote -
alt ⊂'()' or other brackets to output (field)
fds[2] ←→ Character field quote -
alt ⊂'<>' or other brackets to output
fds[3
Hi,
I can look into this. However, how shall we handle character
arrays with rank > 1?
Quotes on every line or one quote at the beginning and one at the
end (for example)?
If the problem is distinguishing numbers and characters then we
co
I agree, and specifically I'd suggest using double quotes for an
encapsulated array of characters, while using single quotes to indicate the
difference between characters and numbers inside an array.
This would be analogous with the GNU APL extension where double quotes
ensures arrays even for sin
Off the cuff, it seems like putting quotes around strings is a really good
idea. How else would you tell the difference between 123 and "123"?
Blake
On Wed, Apr 13, 2016 at 2:34 AM, Elias Mårtenson wrote:
> Given the following expression:
>
> * 8⎕CR 2 2⍴10 'foo' 20 'bar'*
> ┌→───┐
> ↓
Given the following expression:
* 8⎕CR 2 2⍴10 'foo' 20 'bar'*
┌→───┐
↓10 ┌→──┐│
│ │foo││
│ └───┘│
│20 ┌→──┐│
│ │bar││
│ └───┘│
└∊───┘
The combination of strings and numbers in the array isn't very pretty.
I'd like to suggest that it renders as following instead:
┌→───┐
12 matches
Mail list logo
