From 82eab51659fa1c0d01c60db26e1b2c030f8f805c Mon Sep 17 00:00:00 2001 From: Mike Long Date: Mon, 18 Dec 2017 19:57:20 +0100 Subject: [PATCH] Update to readme to correct misinformation on C standard It turns out that nested functions are a gcc thing - not standard C. Closes #34 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 5d4ca5c..e38d3df 100644 --- a/README.md +++ b/README.md @@ -376,7 +376,7 @@ The basic mechanism that FFF provides you in this case is the custom_fake field You need to create a custom function (e.g. getTime_custom_fake) to produce the output optionally by use of a helper variable (e.g. getTime_custom_now) to retrieve that output from. Then some creativity to tie it all together. The most important part (IMHO) is to keep your test case readable and maintainable. -In case your project uses a C99 compliant C compiler you can even combine all this in a single unit test function so you can easily oversee all details of the test. See the example below. +In case your project uses a C compiler that supports nested functions (e.g. GCC) you can even combine all this in a single unit test function so you can easily oversee all details of the test. ```c /* The time structure */