From eab9e58e7e6b815e7dfb288510b49d52fe579fe2 Mon Sep 17 00:00:00 2001
From: Chris Ward <chris.ward@ethereum.org>
Date: Wed, 16 Jan 2019 17:11:23 +0200
Subject: Add call warning into main docs and remove FAQ item

---
 docs/frequently-asked-questions.rst | 12 ------------
 1 file changed, 12 deletions(-)

(limited to 'docs/frequently-asked-questions.rst')

diff --git a/docs/frequently-asked-questions.rst b/docs/frequently-asked-questions.rst
index 4635d577..3b59af81 100644
--- a/docs/frequently-asked-questions.rst
+++ b/docs/frequently-asked-questions.rst
@@ -54,18 +54,6 @@ Yes, you can use ``abi.encodePacked``::
         }
     }
 
-
-Why is the low-level function ``.call()`` less favorable than instantiating a contract with a variable (``ContractB b;``) and executing its functions (``b.doSomething();``)?
-=============================================================================================================================================================================
-
-If you use actual functions, the compiler will tell you if the types
-or your arguments do not match, if the function does not exist
-or is not visible and it will do the packing of the
-arguments for you.
-
-See `ping.sol <https://github.com/fivedogit/solidity-baby-steps/blob/master/contracts/45_ping.sol>`_ and
-`pong.sol <https://github.com/fivedogit/solidity-baby-steps/blob/master/contracts/45_pong.sol>`_.
-
 What happens if you send ether along with a function call to a contract?
 ========================================================================
 
-- 
cgit