[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-apl] Suggested change in rendering of ⎕CR

From: Blake McBride
Subject: Re: [Bug-apl] Suggested change in rendering of ⎕CR
Date: Wed, 13 Apr 2016 19:48:25 -0500

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 <address@hidden> wrote:

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 could also use a different
frame type (like bold or double-line for characters). That would also be closer to the "normal"
display of APL values (the quotes are input-only).

/// Jürgen

On 04/13/2016 02:38 PM, Elias Mårtenson wrote:

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 single characters.

I'm on mobile now so I can't really make any good examples. But I'm hoping you'll understand what I mean.


On 13 Apr 2016 8:26 p.m., "Blake McBride" <address@hidden> wrote:
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"?


On Wed, Apr 13, 2016 at 2:34 AM, Elias Mårtenson <address@hidden> wrote:
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:

↓   ┌→──┐│
│10 │foo││
│   └───┘│
│   ┌→──┐│
│20 │bar││
│   └───┘│

I would also like to see another ⎕CR mode that would render it like below, as this would make displaying arrays with lots of strings (in my case, database table content) much easier to read:

10 "foo"│
│20 "bar"│

Jürgen, what's your opinion on this?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]