Re: [TUHS] bas(1) and bs(1) videos including features and use

Re: [TUHS] bas(1) and bs(1) videos including features and use

[M Douglas McIlroy]

[-- Attachment #1: Type: text/plain, Size: 262 bytes --]

Nice archaeology. Blinded by my distaste for Basic , I never bothered to
try bs--and should have. Dave has highlighted features that deserve respect.
One telling example suggests this should be legalized in C:
        printf("%s\n", {"true", "false"}[1]);

Doug

[-- Attachment #2: Type: text/html, Size: 362 bytes --]

Re: [TUHS] bas(1) and bs(1) videos including features and use

[Dave Horsfall]

[-- Attachment #1: Type: text/plain, Size: 483 bytes --]

On Wed, 20 Jan 2021, M Douglas McIlroy wrote:

> Nice archaeology. Blinded by my distaste for Basic , I never bothered to try
> bs--and should have. Dave has highlighted features that deserve respect.One
> telling example suggests this should be legalized in C:
>         printf("%s\n", {"true", "false"}[1]);

That would evaluate to a constant being printed (it's a direct array 
reference).  Did you mean something like "...[i]" instead?  That would 
indeed be neat...

-- Dave

Re: [TUHS] bas(1) and bs(1) videos including features and use

[Hellwig Geisse]

On Do, 2021-01-21 at 09:17 +1100, Dave Horsfall wrote:
>         printf("%s\n", {"true", "false"}[1]);
> That would evaluate to a constant being printed (it's a direct array 
> reference).  Did you mean something like "...[i]" instead?  That would 
> indeed be neat...
> 

I think it doesn't matter if the index expression is
a constant expression or not. The point here, as I
understood, is the definition of an unnamed (and not
explicitly typed) array "on the fly".

Hellwig

Re: [TUHS] bas(1) and bs(1) videos including features and use

[Sudipto Mallick]

Then what about the following? :D

    union huh { uint64_t l; double d; };
    uint64_t a = ((union huh){ .d = foo }).l;

--Sudipto Mallick

Re: [TUHS] bas(1) and bs(1) videos including features and use

[Dave Horsfall]

[-- Attachment #1: Type: text/plain, Size: 502 bytes --]

On Thu, 21 Jan 2021, Hellwig Geisse wrote:

>> That would evaluate to a constant being printed (it's a direct array  
>> reference).  Did you mean something like "...[i]" instead?  That would  
>> indeed be neat...
>
> I think it doesn't matter if the index expression is a constant 
> expression or not. The point here, as I understood, is the definition of 
> an unnamed (and not explicitly typed) array "on the fly".

Ah, I see; thanks.  Sometimes I'm too pedantic for my own good :-)

-- Dave

[TUHS] bas(1) and bs(1) videos including features and use

[Dave Plonka]

Hi folks,

In case you're interested:

I've published a couple videos on these ancient Unix tools, sharing
including some language details and showing them in action on v7 and
System III, respectively:

Ken Thompson's bas(1): https://youtu.be/LZUMNZTUJos

Dick Haight's bs(1): https://youtu.be/ELICIa3L22o

Thanks much for the help from TUHS, Mashey, Kernighan, McIlroy, and
others cited therein.

Peace,
Dave

-- 
dave@plonka.us  http://www.cs.wisc.edu/~plonka/

Re: [TUHS] bas(1) and bs(1) videos including features and use

[Andy Kosela]

On Wednesday, January 20, 2021, Dave Plonka <dave@plonka.us> wrote:
>
> Hi folks,
>
> In case you're interested:
>
> I've published a couple videos on these ancient Unix tools, sharing
> including some language details and showing them in action on v7 and
> System III, respectively:
>
> Ken Thompson's bas(1): https://youtu.be/LZUMNZTUJos
>
> Dick Haight's bs(1): https://youtu.be/ELICIa3L22o
>
> Thanks much for the help from TUHS, Mashey, Kernighan, McIlroy, and
> others cited therein.


Great content!  I love YouTube channels about retrocomputing.  You've
just earned a new subscriber.

Thanks!

--Andy