Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c > #403464

Re: why &| dont work and its possible to make it work

Path csiph.com!eternal-september.org!feeder.eternal-september.org!nntp.eternal-september.org!.POSTED!not-for-mail
From David Brown <david.brown@hesbynett.no>
Newsgroups comp.lang.c
Subject Re: why &| dont work and its possible to make it work
Date Fri, 23 Oct 2026 08:55:06 +0200
Organization A noiseless patient Spider
Lines 24
Message-ID <11bf0ca$1eo7q$1@dont-email.me> (permalink)
References <117mere$3a14a$1@dont-email.me> <11bda5e$vdh3$1@dont-email.me> <%EtCS.3$dnHe.0@fx46.iad>
MIME-Version 1.0
Content-Type text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding 7bit
Injection-Date Fri, 23 Oct 2026 06:55:07 +0000 (UTC)
Injection-Info dont-email.me; logging-data="1532154"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18N+4gYGRLW0UFO8ISpBwNmCXQwhfRKSLQ="; posting-host="7400fcdb32ce88f15c58e9bcb96ebcf6"
User-Agent Mozilla Thunderbird
Cancel-Lock sha1:IOs68oyuzlfKQLLzIMoVaa24MOM= sha256:2shcMP6XZVSVZdoJ8GIzl2pQ5pzFSGf5eGk3JvGMMQI= sha1:uq8x8KhT9BQqL7dnbxJteDhWpJI= sha256:WOFbtc4U9OjR+4MQHYzY7rRZhJUvJry0yLHGS4M8gYU=
In-Reply-To <%EtCS.3$dnHe.0@fx46.iad>
Content-Language en-GB, nb-NO
Xref csiph.com comp.lang.c:403464

Show key headers only | View raw

On 22/10/2026 21:40, Scott Lurndal wrote:
> fir <profesor.fir@gmail.com> writes:
>> sady this plan of using | & failed becouse its said that here for example
>>
>>      if(target<0 ||target>=bag_max ||!bag[target].enabled)   {}
>>
>> if target is -1 in case of | the last one will be evalueated too
>> and it may be segfault
> 
> If the first test is true, the remaining tests will not be
> executed.
> 
> If you knew C, you'd have known that.

You missed the point.  || and && is ugly and for common, stupid people. 
Creative programmers like Fir need to be able to use whatever syntax 
they like at the time, and the compiler should know what they mean - the 
compiler should /know/ that when Fir writes |, he means ||.  It should 
be able to tell he means logical or, not bitwise or, and figure out 
which order the expressions should be evaluated regardless of how he 
writes them.

Anything else is just a critical flaw in C.

Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

why &| dont work and its possible to make it work fir <profesor.fir@gmail.com> - 2026-09-07 15:39 +0200
  Re: why &| dont work and its possible to make it work bart <bc@freeuk.com> - 2026-09-07 16:42 +0100
    Re: why &| dont work and its possible to make it work fir <profesor.fir@gmail.com> - 2026-09-07 18:14 +0200
    Re: why &| dont work and its possible to make it work Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-09 07:14 +0000
      Re: why &| dont work and its possible to make it work Bonita Montero <Bonita.Montero@gmail.com> - 2026-09-09 11:15 +0200
      Re: why &| dont work and its possible to make it work bart <bc@freeuk.com> - 2026-09-09 11:23 +0100
        Re: why &| dont work and its possible to make it work fir <profesor.fir@gmail.com> - 2026-09-09 13:28 +0200
          Re: why &| dont work and its possible to make it work fir <profesor.fir@gmail.com> - 2026-09-09 14:01 +0200
  Re: why &| dont work and its possible to make it work Bonita Montero <Bonita.Montero@gmail.com> - 2026-09-07 17:49 +0200
    Re: why &| dont work and its possible to make it work fir <profesor.fir@gmail.com> - 2026-09-07 18:22 +0200
    Re: why &| dont work and its possible to make it work Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-09 06:07 +0000
  Re: why &| dont work and its possible to make it work Kaz Kylheku <046-301-5902@kylheku.com> - 2026-09-10 20:13 +0000
  Re: why &| dont work and its possible to make it work fir <profesor.fir@gmail.com> - 2026-10-22 17:29 +0200
    Re: why &| dont work and its possible to make it work scott@slp53.sl.home (Scott Lurndal) - 2026-10-22 19:40 +0000
      Re: why &| dont work and its possible to make it work Kaz Kylheku <046-301-5902@kylheku.com> - 2026-10-22 20:13 +0000
        Re: why &| dont work and its possible to make it work fir <profesor.fir@gmail.com> - 2026-10-22 23:13 +0200
          Re: why &| dont work and its possible to make it work fir <profesor.fir@gmail.com> - 2026-10-22 23:28 +0200
      Re: why &| dont work and its possible to make it work fir <profesor.fir@gmail.com> - 2026-10-22 22:46 +0200
      Re: why &| dont work and its possible to make it work David Brown <david.brown@hesbynett.no> - 2026-10-23 08:55 +0200
        Re: why &| dont work and its possible to make it work fir <profesor.fir@gmail.com> - 2026-10-23 09:39 +0200
          Re: why &| dont work and its possible to make it work fir <profesor.fir@gmail.com> - 2026-10-23 09:44 +0200
            Re: why &| dont work and its possible to make it work fir <profesor.fir@gmail.com> - 2026-10-23 09:51 +0200
              Re: why &| dont work and its possible to make it work David Brown <david.brown@hesbynett.no> - 2026-10-23 11:23 +0200
                Re: why &| dont work and its possible to make it work fir <profesor.fir@gmail.com> - 2026-10-23 14:25 +0200
      Re: why &| dont work and its possible to make it work "chine.bleu" <chine.bleu@yahoo.com> - 2026-10-24 03:16 -0700
        Re: why &| dont work and its possible to make it work fir <profesor.fir@gmail.com> - 2026-10-24 15:00 +0200
        Re: why &| dont work and its possible to make it work Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-10-24 22:22 +0000

csiph-web