Interest in building zxing-cpp with disabled exception handling? #710

axxel · 2024-02-01T11:18:39Z

axxel
Feb 1, 2024
Maintainer

Sparked by #708 I looked briefly into the subject of disabling exception handling (-fno-exceptions in gcc and clang speak). I see 3 options regarding this subject:

exceptions are part of the API/ABI and compilation with disabled exception handling of either library and client code is not officially supported. (status quo)
there is a build option for zxing-cpp that allows to disable exception handling for client code with some some major caveats, like only available for the reader API. (relatively easy to implement)
there is a build option/API redesign that completely removes exception handling from the code base. (not going to happen)

Now my question is basically whether option 2 is worth spending time on?

What is your stance on exception handling?

I have no problem with c++ exception hadling.

80%

I'd rather not enable exception handling in my client code just because zxing-cpp requires it.

20%

I can't use zxing-cpp if exception handling is required in my client code.

0%

Exceptions are evil/unsupported, no zxing-cpp as long as there is any exception handling involved.

0%

5 votes

duanqn · 2024-02-02T03:24:03Z

duanqn
Feb 2, 2024

I read about -fno-exceptions here and it seems like it is a GNU extension to the standard C++. If so, then it should not be a requirement for ZXing-cpp to support a non-standard language extension.

It is also specifically noted in the manual that

If you might have some code that throws, you shouldn't use -fno-exceptions. If you have some code that uses try or catch, you shouldn't use -fno-exceptions.

Also, I think it is possible for any downstream app to consume ZXing-cpp with an extra wrapper layer, like

// wrapper.cpp
// compile with -fexceptions
try{
  // wrap all ZXing-cpp calls in here
}
catch(...){
  // Do something or do nothing at all
}

and compile the rest of their source files with -fno-exceptions

1 reply

duanqn Feb 2, 2024

Maybe we need to move any function implementation involving exceptions to .cpp files, though. Otherwise they would get compile errors when they include the header.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

Interest in building zxing-cpp with disabled exception handling? #710

Uh oh!

{{title}}

Uh oh!

Replies: 1 comment 1 reply

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Uh oh!

Interest in building zxing-cpp with disabled exception handling? #710

Uh oh!

axxel Feb 1, 2024 Maintainer

Replies: 1 comment · 1 reply

Uh oh!

duanqn Feb 2, 2024

Uh oh!

duanqn Feb 2, 2024

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

axxel
Feb 1, 2024
Maintainer

Replies: 1 comment 1 reply

duanqn
Feb 2, 2024