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


Groups > comp.lang.c++ > #89563

Re: Why no structured bings in catch()?

From Muttley@dastardlyhq.com
Newsgroups comp.lang.c++
Subject Re: Why no structured bings in catch()?
Date 2023-03-09 09:12 +0000
Organization A noiseless patient Spider
Message-ID <tuc7th$1cl8k$1@dont-email.me> (permalink)
References (1 earlier) <8966b5ac-bfca-492d-b1d9-da7fe0032c8dn@googlegroups.com> <tu9sgq$t404$1@dont-email.me> <cone.1678277585.903048.160444.1004@monster.email-scan.com> <tuacml$vrgq$1@dont-email.me> <cone.1678322351.933124.195471.1004@monster.email-scan.com>

Show all headers | View raw


On Wed, 08 Mar 2023 19:39:11 -0500
Sam <sam@email-scan.com> wrote:
>Muttley@dastardlyhq.com writes:
>
>> On Wed, 08 Mar 2023 07:13:05 -0500
>> Sam <sam@email-scan.com> wrote:
>> >Muttley@dastardlyhq.com writes:
>> >
>> >> >How can the compiler know what that exception could possibly be?
>> >> >It has none of information at all. The throw can be anywhere far up
>> >>
>> >> Of course it has the information. It knows whats been thrown so it knows
>> >> if it can be captured in a structure binding.
>> >
>> >It only knows what's thrown at runtime. Not at compile time. It is
>>
>> It knows what is thrown at runtime.
>> It knows what *could* be thrown at compile time.
>
>No, it doesn't. If foo() calls bar() from another translation unit, there's  
>no information available to compiler to indicate what bar() could possibly  
>throw.
>
>One of the biggest C++ design fuckups was the screwed up throw-specifiers,  
>that basically meant nothing useful, and they're now completely gone.
>
>C++ should've handled throw specifiers the same way Java does, making it  
>possible to guarantee /at compile time/ that all exceptions get handled,
>
>> And if it knows what could be thrown and what catch statements are  
>> encompassing
>> those throws then it could compile in suitable types for an auto in the  
>> catch.
>
>I'll write the bar(), you write the foo(), and we'll see if you know what  
>I'm throwing.

Once something is thrown the runtime knows what it is and simply has to 
match it with a catch as it does now. I'm not pretending matching an auto
would be simple but I don't see why it should be impossible. After all, the
runtime has to differentiate between int, char, parent and child classes to
do proper catching.

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


Thread

Why no structured bings in catch()? Muttley@dastardlyhq.com - 2023-03-08 10:04 +0000
  Re: Why no structured bings in catch()? Öö Tiib <ootiib@hot.ee> - 2023-03-08 03:23 -0800
    Re: Why no structured bings in catch()? Muttley@dastardlyhq.com - 2023-03-08 11:45 +0000
      Re: Why no structured bings in catch()? Sam <sam@email-scan.com> - 2023-03-08 07:13 -0500
        Re: Why no structured bings in catch()? Muttley@dastardlyhq.com - 2023-03-08 16:21 +0000
          Re: Why no structured bings in catch()? Bo Persson <bo@bo-persson.se> - 2023-03-08 19:21 +0100
          Re: Why no structured bings in catch()? Sam <sam@email-scan.com> - 2023-03-08 19:39 -0500
            Re: Why no structured bings in catch()? Muttley@dastardlyhq.com - 2023-03-09 09:12 +0000
              Re: Why no structured bings in catch()? Bonita Montero <Bonita.Montero@gmail.com> - 2023-03-09 10:16 +0100
              Re: Why no structured bings in catch()? Paavo Helde <eesnimi@osa.pri.ee> - 2023-03-09 14:06 +0200
              Re: Why no structured bings in catch()? Sam <sam@email-scan.com> - 2023-03-10 06:58 -0500
      Re: Why no structured bings in catch()? Andrey Tarasevich <andreytarasevich@hotmail.com> - 2023-03-08 14:55 -0800
  Re: Why no structured bings in catch()? Bonita Montero <Bonita.Montero@gmail.com> - 2023-03-08 18:28 +0100
    Re: Why no structured bings in catch()? Muttley@dastardlyhq.com - 2023-03-09 09:13 +0000
      Re: Why no structured bings in catch()? Öö Tiib <ootiib@hot.ee> - 2023-03-09 03:18 -0800
      Re: Why no structured bings in catch()? Bonita Montero <Bonita.Montero@gmail.com> - 2023-03-09 17:06 +0100
      Re: Why no structured bings in catch()? Christian Gollwitzer <auriocus@gmx.de> - 2023-03-10 08:12 +0100
        Re: Why no structured bings in catch()? Muttley@dastardlyhq.com - 2023-03-10 10:05 +0000
          Re: Why no structured bings in catch()? Öö Tiib <ootiib@hot.ee> - 2023-03-10 05:04 -0800
            Re: Why no structured bings in catch()? Muttley@dastardlyhq.com - 2023-03-10 16:14 +0000
  Re: Why no structured bings in catch()? Daniel <danielaparker@gmail.com> - 2023-03-09 11:38 -0800
    Re: Why no structured bings in catch()? Muttley@dastardlyhq.com - 2023-03-10 10:03 +0000

csiph-web