[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Exception safety of generated C++ parser
From: |
Akim Demaille |
Subject: |
Re: Exception safety of generated C++ parser |
Date: |
Wed, 19 Sep 2012 16:01:01 +0200 |
Le 13 sept. 2012 à 17:54, Oleksii Taran a écrit :
> Hello
>
> Does Bison guarantees exception safety in C++ parser, i.e. will it make
> any clean-up and free memory if an exception is thrown on rule action? I
> know about %destructor directive, but it seems irrelevant, since
> destructor code is called only if parser recovers from _syntax_ error.
hi Oleskii,
Sorry for the delays.
Yes, I agree that the current implementation is not satisfying on this
regard. IMHO, the %destructors should be called when an exception is
rised, exactly as if the parsing was ended on a syntax error. Would that
match your expectations? Would you be ready to try patches we might
submit?
- Exception safety of generated C++ parser, Oleksii Taran, 2012/09/13
- Re: Exception safety of generated C++ parser, Hans Aberg, 2012/09/13
- Re: Exception safety of generated C++ parser,
Akim Demaille <=
- Re: Exception safety of generated C++ parser, Oleksii Taran, 2012/09/19
- Re: Exception safety of generated C++ parser, Akim Demaille, 2012/09/20
- Re: Exception safety of generated C++ parser, Oleksii Taran, 2012/09/20
- Re: Exception safety of generated C++ parser, Akim Demaille, 2012/09/21
- Re: Exception safety of generated C++ parser, Oleksii Taran, 2012/09/24
- Re: Exception safety of generated C++ parser, Akim Demaille, 2012/09/24
- Re: Exception safety of generated C++ parser, Akim Demaille, 2012/09/26
- Re: Exception safety of generated C++ parser, Oleksii Taran, 2012/09/28
- Re: Exception safety of generated C++ parser, Oleksii Taran, 2012/09/28