From 94620108d3dbdb8c2fd11fbf8dbe12bba321ee72 Mon Sep 17 00:00:00 2001 From: jvoisin Date: Wed, 1 Apr 2020 17:09:36 +0200 Subject: Document why SP doesn't provide a `.nop` action --- doc/source/faq.rst | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/doc/source/faq.rst b/doc/source/faq.rst index 285f0c8..3c09409 100644 --- a/doc/source/faq.rst +++ b/doc/source/faq.rst @@ -245,3 +245,19 @@ if someone can manage to get better results than us. The possibility of having this natively in PHP has `been discussed `_, but as 2017, nothing has been merged yet. + +Nop'ing function execution +"""""""""""""""""""""""""" + +Snuffleupagus can be configured to either *allow* or *drop* the execution of +particular functions and optionally *log* and *dump* them, but it doesn't +provide any mechanism to *nop* their execution. + +We thought about adding this, but didn't for several reasons: + +- What should the return value of a *nop'ed* function be? +- It would add confusion between ``drop``, ``nop`` and ``log``. +- Usually, when a specific function is called, either it's a dangerous one + and you want to stop the execution immediately, or you want to let it + continue and log it. There isn't really any middle-ground, or at least we + failed to find any. -- cgit v1.3