XSB and AVL trees

From: "menyounglee@xxxxxxxxx" <menyounglee@xxxxxxxxx>
Date: 30 Aug 2005 12:51:05 -0700

The XSB System Manual lacks full documentation for AVL-trees despite
having a entry for it. (see
http://xsb.sourceforge.net/manual2/node30.html)

Can anyone tell me how to access the library (like, what's the module
called?)

.

Prev by Date: Re: Help: Multiple Proof Trees
Next by Date: Re: ...Thanks for recommending that book!
Previous by thread: Bug on XSB prolog???
Next by thread: how to start?
Index(es):
- Date
- Thread

Relevant Pages

Re: XSB and AVL trees
... > The XSB System Manual lacks full documentation for AVL-trees despite ... > having a entry for it. ...
(comp.lang.prolog)
Re: Executable enty points incorrectly documented
... I was speaking about Windows SDK not MSDN Library entirely, but even if Windows SDK conatins C/C++ documentation I believe that main/WinMain belong to C/C++ documentation rather than Windows API documentation. ... It's correct about the default entry point names used by the linker and also correct about what those entry points call and because this is the ...
(microsoft.public.win32.programmer.kernel)
Re: Executable enty points incorrectly documented
... The function signature is there though ... belong to C/C++ documentation rather than Windows API documentation. ... As for the entry point signature: ...
(microsoft.public.win32.programmer.kernel)
Re: Executable enty points incorrectly documented
... All these things are correct but this is more specific and related to the .NET Framework than to Windows API and the C++ linker and does not mention the actual entry point signatures either. ... The documentation problem to which you allude is that it is the CRT entry point that calls one of the versions of main / WinMain that is defined in your program. ... This is the signature of the managed entry point that has nothing to do with native executables/DLLs. ...
(microsoft.public.win32.programmer.kernel)
Re: Executable enty points incorrectly documented
... .NET Framework than to Windows API and the C++ linker and does not mention ... the actual entry point signatures either. ... The documentation problem to which you allude is that it is the CRT entry ... This is the signature of the managed entry point (as it is stated ...
(microsoft.public.win32.programmer.kernel)