From 609bcd159f2746b10de4f021f714bd8e6515f125 Mon Sep 17 00:00:00 2001 From: Patrick Pelissier Date: Sun, 26 Feb 2017 23:47:32 +0100 Subject: [PATCH] Update doc --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index de063c13..5f92f917 100644 --- a/README.md +++ b/README.md @@ -54,7 +54,7 @@ Otherwise you may have a noticeable slow-down (up to a factor x10 in some cases) M\*LIB is distributed under BSD-2 simplified license. It is strongly advised not to read the source to know how to use the library -but rather read the examples. +but rather read the examples or the tests. Components ---------- @@ -232,7 +232,7 @@ When using M\*LIB, sometimes (often) the list of errors/warnings generated by th even if the error itself is minor. This is more or less the same as the use of template in C++. You should focus mainly on the first reported error/warning even if the link between what the compiler said and what the error is is not immediate: -for example, a lack of inclusion of an header, an unkown oplist, a missing argument, a missing method in an oplist, ... +for example, a lack of inclusion of an header, an unkown oplist, a missing argument, a missing method in an oplist, ... Another way to debug is to generate the preprocessed file (by usuallt calling the compiler with the '-E' option instead of '-c') and check what's wrong in the preprocessed file. The final goal of the library is to be able to write code like this in pure C while keeping type safety and compile time name resolution: