diogo/yap-6.3
Archived
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

add Yap_ReadBuffer

Browse Source 
git-svn-id: https://yap.svn.sf.net/svnroot/yap/trunk@1064 b08c6af1-5177-4d33-ba66-4b1c6b8b522a
This commit is contained in:
vsc
2004-05-14 16:33:47 +00:00
parent 19bfe301db
commit 0aa358a2b7
8 changed files with 145 additions and 64 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
docs/yap.tex
View File

@@ -5627,11 +5627,11 @@ signal name or one that is not supported on this platform. No checks
are made on the handler provided by the user.
@table @code
@item SIGHUP (Hangup)
sig_hup in YAP; Reconsult the initialization files
@item sig_up (Hangup)
SIGHUP in Unix/Linux; Reconsult the initialization files
~/.yaprc, ~/.prologrc and ~/prolog.ini.
@item SIGUSR1 and SIGUSR2 (User signals)
sig_usr1 and sig_usr2 in YAP; Print a message and halt.
@item sig_usr1 and sig_usr2 (User signals)
SIGUSR1 and SIGUSR2 in Unix/Linux; Print a message and halt.
@end table
A special case is made, where if @var{Callable} is bound to
@@ -13585,6 +13585,17 @@ character atoms
@noindent
The user-provided string must include a terminating null character.
@findex YAP_ReadBuffer (C-Interface function)
The C-interface function calls the parser on a sequence of characters
stored at @var{buf} and returns the resulting term.
@example
YAP_Term YAP_ReadBuffer(char *@var{buf},YAP_Term *@var{error})
@end example
@noindent
The user-provided string must include a terminating null
character. Syntax errors will cause returning @code{FALSE} and binding
@var{error} to a Prolog term.
@node Memory Allocation, Controlling Streams, Manipulating Strings, C-Interface
@section Memory Allocation