Dave Gomboc <[EMAIL PROTECTED]> wrote: > [Fernando Cacciola] >> The most fundamental point is that being Haskell a pure functional >> language there is no possibly undefined behaviour to worry about, >> so Maybe doesn't need to address this issue as optional<> does. > ... and later ... >> I account the possibly undefined behavior of accesing an uninitialized >> optional as a real and important problem. > > You can get rid of the possibly undefined behaviour by defining it! Throw > an exception when there's an attempted coercion from nil/undefined to a > normal value.
Exactly! -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
