From: Markus Elfring <Markus.Elfring@web.de>
To: Oliver Bandel <oliver@first.in-berlin.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Detecting missed checks for error indications in ML code
Date: Sun, 24 Jan 2021 17:21:58 +0100 [thread overview]
Message-ID: <a775ca82-b401-3642-8921-1e81f4602da1@web.de> (raw)
In-Reply-To: <20210124160729.iybuih6mmaquulcw@first.in-berlin.de>
>> I am looking more for possibilities to avoid missed checks for return values
>> from some function calls.
>
> I'm not sure what your problem is, which you want to solve.
> Do you want to improve your programming (aka "coding") style?
> Or do you have to deal with some code written by other people
> and you fear that it's not using the type system to avoid the
> problem of unclear (in the sense of "real value" vs. "error indicating
> value") return values?
Both.
Are you used to programming concerns according to software weaknesses
like “CWE-252: Unchecked Return Value”?
https://cwe.mitre.org/data/definitions/252.html
>>> Since a while OCaml also offers a result-type, which you can use.
>>
>> Do any programming interfaces need still to work without this special data type?
>
> ? Don't understand your question.
Do you get further development ideas from another API example?
https://ocaml.org/releases/4.11/htmlman/libref/UnixLabels.html#VALsystem
Regards,
Markus
next prev parent reply other threads:[~2021-01-24 16:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 11:42 Markus Elfring
2021-01-24 14:08 ` Hendrik Boom
2021-01-24 15:28 ` Markus Elfring
2021-01-24 14:34 ` Oliver Bandel
2021-01-24 15:52 ` Markus Elfring
2021-01-24 16:07 ` Oliver Bandel
2021-01-24 16:21 ` Markus Elfring [this message]
2021-01-25 3:59 ` Yawar Amin
2021-01-25 18:55 ` Markus Elfring
2021-01-24 16:18 ` Oliver Bandel
2021-01-24 16:50 ` Markus Elfring
2021-01-29 21:14 ` [Caml-list] Error handling in FPLs (Re: Detecting missed checks for error indications in ML code) Oliver Bandel
2021-01-30 11:51 ` Markus Elfring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a775ca82-b401-3642-8921-1e81f4602da1@web.de \
--to=markus.elfring@web.de \
--cc=caml-list@inria.fr \
--cc=oliver@first.in-berlin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).