File: no_optional_interface.qbk

package info (click to toggle)
boost1.90 1.90.0-5
  • links: PTS, VCS
  • area: main
  • in suites: forky
  • size: 593,168 kB
  • sloc: cpp: 4,190,642; xml: 196,648; python: 34,618; ansic: 23,145; asm: 5,468; sh: 3,776; makefile: 1,162; perl: 1,020; sql: 728; ruby: 676; yacc: 478; java: 77; lisp: 24; csh: 6
file content (34 lines) | stat: -rw-r--r-- 1,506 bytes parent folder | download | duplicates (8)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
[/
  Copyright (c) Vladimir Batov 2009-2022
  Distributed under the Boost Software License, Version 1.0.
  See copy at http://www.boost.org/LICENSE_1_0.txt.
]

[section Alternative Interface]

[:[*['"It's not a question of happiness, it's a requirement. Consider the alternativeā€ Doug Horton]]]

As it was indicated previously [@boost:/libs/optional/index.html `boost::optional`] is the actual type returned by the `boost::convert()` main interface:

 boost::optional<TypeOut> boost::convert(TypeIn const&, Converter const&);

The signature is ['functionally-complete] and routinely elided during compilation. Still, the following alternative (and arguably more traditional) interface might be potentially more suitable for certain deployment scenarios (or due to personal preferences):

 TypeOut convert(TypeIn const&, Converter const&, TypeOut const& fallback_value);
 TypeOut convert(TypeIn const&, Converter const&, Functor const& fallback_func);
 TypeOut convert(TypeIn const&, Converter const&, boost::throw_on_failure);

The interface still provides unambiguous behavior and readability, full support for various program flows and various degrees of conversion-failure detection and processing. It can be deployed in a similar fashion as follows:

[getting_serious_example5]
[getting_serious_example7]

Still, the described interfaces are convenience wrappers around the main interface which provides the described behavior with:

[getting_serious_example8]

[endsect] [/section Return Value]