doc changes

C/cmppreds.c

@@ -683,6 +683,7 @@ p_acomp( USES_REGS1 )
 }
 
 /**
+  @[
    @class arith_eq_2
    @brief  =:=/2: Equality of arithmetic expressions
 
@@ -726,6 +727,8 @@ a_eq(Term t1, Term t2)
 }
 
 /**
+   @}
+
    @class arith_dif_2
    @brief  =\\=/2: Difference of arithmetic expressions
 

CXX/yapi.hh

@@ -367,7 +367,9 @@ class YAPParams;
  */
 class YAPEngine {
 public:
-	YAPEngine(YAPParams const& params);
+  YAPEngine(YAPParams const& params);
+  query( char *s ) { return new Query( s ); }
+  atom( char *s ) { return new Query( s ); }
 };
 
 /**

docs/doxygen.rc

@@ -746,7 +746,7 @@ WARN_LOGFILE =
 # spaces.
 # Note: If this tag is empty the current directory is searched.
 
-INPUT                  = docs/yap.md pl/absf.yap C/cmppreds.c C/eval.c H/eval.h C/arith0.c C/arith1.c C/arith2.c pl/arithpreds.yap CXX
+INPUT                  = docs/yap.md pl/absf.yap C/cmppreds.c C/eval.c H/eval.h C/arith0.c C/arith1.c C/arith2.c pl/arithpreds.yap CXX packages/real library/dialect/swi/fli/
 
 # This tag can be used to specify the character encoding of the source files
 # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses

docs/texi2doxy

@@ -281,12 +281,12 @@ process("@item", Line, Rest, NewLine , FilePos) :-
 	(
 	    Env = "@table",
 	     atom_string( A, Line ),
-	     pred( _Pred, Key, A, FilePos )
+	     pred( _Pred, _Key, A, FilePos )
 	     ->
 		 push( list, it(Env, Item, Pos, NNumb) ),
 		 (
 		     % sendout the comand
-		     format(string(NewLine), '~t~s ~*+<li>~s @anchor ~a', [Marker, Pos1, First,  Key]),
+		     format(string(NewLine), '~t~s ~*+<li>~s @anchor ~a', [Marker, Pos1, First,  _Key]),
 		     push( indent, done )	
 			 ;
 			 NewLine = force
@@ -601,8 +601,8 @@ simplify( [0'q,0'Q|L]) --> "=", !,
 	  simplify(L).
 simplify( [0'q,0'U|L]) --> "?", !,
 	  simplify(L).
-simplify( [0'_|L]) --> "/", !,
-	  simplify(L).
+simplify( [] ) --> "/", !.
+%	  simplify(L).
 simplify( [0's,0'S|L]) --> "<", !,
 	  simplify(L).
 simplify( [0'u,0'U|L]) --> "\v", !,

docs/yap.tex

@@ -6830,6 +6830,7 @@ attributes from other known solvers/modules via the module prefix in
 * CLPR Non-linear Constraints::               
 @end menu
 
+
 @include clpr.tex
 
 @node CHR, Logtalk, CLPR, Top
@@ -6856,7 +6857,7 @@ systems or by using the @code{Logtalk - YAP} shortcut in the Logtalk
 program group in the Start Menu on Windows systems. For more information 
 please see the URL @url{http://logtalk.org/}.
 
-@node MYDDAS, Threads, Logtalk, Extensions
+@node MYDDAS, Real, Logtalk, Extensions
 @section MYDDAS
 @cindex MYDDAS
 
@@ -7608,8 +7609,20 @@ action, report an error, we could use the following SQL mode.
 You can see the available SQL Modes at the MySQL homepage at
 @url{http://www.mysql.org}.
 
-@node Threads, Parallelism, MYDDAS, Extensions
-@section Threads
+@node Real, Threads, MYDDAS, Extensions
+
+@chapter Real::   Talking to the R language 
+
+@ifplaintext
+
+Please have a look at @subpage RealPage
+
+@copydoc real
+
+@end ifplaintext
+
+@node Threads, Parallelism, Real, Extensions
+@chapter Threads
 
 YAP implements a SWI-Prolog compatible multithreading
 library. Like in SWI-Prolog, Prolog threads have their own stacks and
@@ -9006,9 +9019,9 @@ being designed to work with the swig (@url(www.swig.org}) interface compiler.
 <ul>
 <li> The original YAP C-interface exports the YAP engine.
 </li>
-<li>The @subpage swi-c-interface emulates Jan Wielemaker's SWI foreign language interface.
+<li>The @ref swi-c-interface emulates Jan Wielemaker's SWI foreign language interface.
 </li>
-<li>The @subpage yap-cplus-interface is desiged to interface with Object-Oriented systems.
+<li>The @ref  yap-cplus-interface is desiged to interface with Object-Oriented systems.
 </li>
 </ul>
 @end ifplaintext

library/dialect/swi/fli/swi.c

@@ -11,23 +11,9 @@
 
 /**
  *
- *   @defgroup swi-c-interface SWI-Prolog Foreign Language Interface.
+ *   @daddtogroup swi-c-interface
  *
- *
- *    @tableofcontents
- *
- * A reimplementation of Jan Wielemaker's SWI-Prolog C-language interface, it supports
- * most of the functionality in the original implementation. It allows for:
- *
- *   - Term Construction, Access, and Unification
- *   - Manipulation of Atoms, Strings, Lists of Codes and Lists of Atoms
- *   - Query evaluation
- *   - Thread and Prolog engine management
- *   - Data-Base Access
- *
- * In this interface, all Prolog data known by C is referenced through term references (term_t), hence
- * Prolog has all the information necessary to perform its memory management without special precautions
- *  from the C programmer.
+ * @{
  */
 
 #define PL_KERNEL 1
@@ -3267,3 +3253,7 @@ int WINAPI win_yap2swi(HANDLE hinst, DWORD reason, LPVOID reserved)
 }
 #endif
 
+/**
+ * @{
+ */
+

library/dialect/swi/fli/swi.h

@@ -1,3 +1,27 @@
+/*************************************************************************
+*									 *
+*	 YAP Prolog 							 *
+*									 *
+*	Yap Prolog was developed at NCCUP - Universidade do Porto	 *
+*									 *
+* Copyright L.Damas, V.S.Costa and Universidade do Porto 1985-2014	 *
+*									 *
+*************************************************************************/
+
+/** 
+  @file swi.h
+
+  @defgroup swi-c-interface SWI-Prolog Foreign Language Interface
+
+  Support for file name resolution through absolute_file_name/3 and
+  friends. These utility built-ins describe a list of directories that
+  are used by load_files/2 to search. They include pre-compiled paths
+  plus user-defined directories, directories based on environment
+  variables and registry information to search for files.
+
+  @{
+  
+ */
 void Yap_swi_install(void);
 void Yap_install_blobs(void);