Re: Top 10 most common hard skills listed on resumes...

On 2024-08-29, Ben Bacarisse <ben@bsb.me.uk> wrote:

Bart <bc@freeuk.com> writes:
>

On 29/08/2024 13:35, Ben Bacarisse wrote:

Bart <bc@freeuk.com> writes:

>

I explained that. LHS and RHS can be identical terms for assignment in
pretty much every aspect, but there are extra constraints on the LHS.

So you use "exactly the same" to mean "exactly the same except for the
differences".

>
No, I do mean exactly the same, both in terms of syntax and (in my
implementations, which are likely typical) internal representation of those
terms.
>
There are no differences other than where the type system says your code is
invalid. So are no differences when considering only valid programs.
>
This program in my language:
>
     42 := 42
>
is valid syntax.

>
So what?  We were talking about assignment in C.  You cut the two
previous quotes where it was clear we were talking about C.  This is not
an honest thing to do.  You are arguing for the sake if it, and in a
dishonest way too.

It's also valid syntax in C, with a constraint violation that can be
"caught later on" in an implementation of C, just like in Bart's
language.

ISO C doesn't say anything about when errors are caught, other than it
being associated with translation phase 7:

  White-space characters separating tokens are no longer significant. Each
  preprocessing token is converted into a token. The resulting tokens are
  syntactically and semantically analyzed and translated as a translation
  unit.

A constraint violtion like the need for an lvalue could be caught during
the activity denoted by "semantically analyzed" rather than that denoted
by "syntactically analyzed" which would count as "later on" with regard
to syntax.

--
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Mastodon: @Kazinator@mstdn.ca