Doc/examples: clarify usage messages

[openocd.git] / doc / manual / style.txt

diff --git a/doc/manual/style.txt b/doc/manual/style.txt
index b4d021658681a7742a1a26e0572e9b1a2cc688cd..87b1e6babcd74baf19f8b743de1e4eb618907b8e 100644 (file)
--- a/doc/manual/style.txt
+++ b/doc/manual/style.txt
@@ -80,6 +80,9 @@ Finally, try to avoid lines of code that are longer than than 72-80 columns:
 - designated initializers (@{ .field = value @})
 - variables declarations should occur at the point of first use
 - new block scopes for selection and iteration statements
+- use malloc() to create dynamic arrays. Do @b not use @c alloca
+or variable length arrays on the stack. non-MMU hosts(uClinux) and
+pthreads require modest and predictable stack usage.
 
 @section styletypes Type Guidelines
 - use native types (@c int or @c unsigned) if the type is not important
@@ -305,7 +308,7 @@ For technical reference material:
    - Else it's a "Config Command" if it must be used before the
      configuration stage completes.
    - For a "Driver", list its name.
-   - Use BNF style regular expressions to define parameters:
+   - Use EBNF style regular expressions to define parameters:
      brackets around zero-or-one choices, parentheses around
      exactly-one choices.
    - Use \@option, \@file, \@var and other mechanisms where appropriate.