From 3716f093a2aa91c6255a1a169ef59b925fcce677 Mon Sep 17 00:00:00 2001 From: eiffel-org Date: Mon, 3 Sep 2018 08:31:04 +0000 Subject: [PATCH] added related pages and articles links. Updated wikipage Interfacing with C and C++. (Signed-off-by:jocelyn). git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@2052 abb3cda0-5349-4a8f-a601-0c33ac3a8c38 --- .../eiffel-external-mechanism/interfacing-c-and-c.wiki | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/documentation/18.07/solutions/other-languages/eiffel-external-mechanism/interfacing-c-and-c.wiki b/documentation/18.07/solutions/other-languages/eiffel-external-mechanism/interfacing-c-and-c.wiki index e5d78379..93383c7c 100644 --- a/documentation/18.07/solutions/other-languages/eiffel-external-mechanism/interfacing-c-and-c.wiki +++ b/documentation/18.07/solutions/other-languages/eiffel-external-mechanism/interfacing-c-and-c.wiki @@ -1,3 +1,5 @@ +[[Property:modification_date|Mon, 03 Sep 2018 08:31:04 GMT]] +[[Property:publication_date|Mon, 03 Sep 2018 08:28:15 GMT]] [[Property:title|Interfacing with C and C++]] [[Property:weight|0]] [[Property:uuid|dcc4e216-307b-46ec-1bc1-a15da8b99469]] @@ -119,5 +121,12 @@ The first condition means that user file names must conform to the path and file Some parts of the validity of external file names may not be able to be determined by an Eiffel compiler and thus ultimately depend upon the evaluation of an external compiler. For example, the Eiffel compiler might not be able to determine whether a particular C file contains valid content. +==Related pages or articles== +{{seealso|
+- [https://www.eiffel.org/doc/solutions/Eiffel_%22external%22_mechanism]
+- [https://www.eiffel.org/article/protecting_objects]
+- [https://www.eiffel.org/article/using_externals_in_multithreaded_applications]
+- [https://www.eiffel.org/article/c_c_calls_and_callbacks]
+}}