re2c scanner generator / Feature Requests / #23 Improve exception safety with smart pointers

#23 Improve exception safety with smart pointers

Milestone: Next Release (example)

Status: closed

Owner: nobody

Labels: None

Priority: 5

Updated: 2015-10-15

Created: 2015-10-13

Creator: Markus Elfring

Private: No

Would you like to wrap any pointer data members with the template class "std::unique_ptr"?

Discussion

Ulya Trofimovich - 2015-10-13

re2c tries to be C++98 compatible.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Markus Elfring - 2015-10-14
  
  How do you think about to reuse the approach by Howard E. Hinnant eventually?
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ulya Trofimovich - 2015-10-13

status: open --> closed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ulya Trofimovich - 2015-10-14

Honestly, I don't understand where in partucular you want to use 'std::unique_ptr'. What pointers should be wrapped in it and why? (You said "any pointer data members", but this seems a really strange thing to do).

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Markus Elfring - 2015-10-15
  
  How do you think about to avoid any risks from an allocation failure for pointers like "rep" and "ptn"?
  
  Would you like to delegate the calling of the delete operator to a smart pointer?
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ulya Trofimovich - 2015-10-15

I prefere to solve memory management problems by using global custom allocator (memory pool, erena, whatever you call it). re2c makes a lot of small allocations/deallocations. Checking for failure in some few cases is a bad idea.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Markus Elfring - 2015-10-15
  
  How should your software react if the exception "std::bad_alloc" will eventually be thrown during the construction for an object of the class like "CharSet"?
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ulya Trofimovich - 2015-10-15

Fail? No memory ---- no DFAs. :)

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.