The Logtalk Handbook¶
- User Manual
- Declarative object-oriented programming
- Main features
- Integration of logic and object-oriented programming
- Integration of event-driven and object-oriented programming
- Support for component-based programming
- Support for both prototype and class-based systems
- Support for multiple object hierarchies
- Separation between interface and implementation
- Private, protected and public inheritance
- Private, protected and public object predicates
- Parametric objects
- High level multi-threading programming support
- Smooth learning curve
- Compatibility with most Prolog systems and the ISO standard
- Logtalk scope
- Event-driven programming
- Multi-threading programming
- Error handling
- Writing and running applications
- Printing messages and asking questions
- Term and goal expansion
- Installing Logtalk
- Prolog integration and migration guide
- Reference Manual
- Control constructs
- Built-in predicates
- Enumerating objects, categories and protocols
- Enumerating objects, categories and protocols properties
- Creating new objects, categories and protocols
- Abolishing objects, categories and protocols
- Objects, categories, and protocols relations
- Event handling
- Multi-threading engines
- Compiling and loading source files
- Built-in methods
- Should I use prototypes or classes in my application?
- Can I use both classes and prototypes in the same application?
- Can I mix classes and prototypes in the same hierarchy?
- Can I use a protocol or a category with both prototypes and classes?
- What support is provided in Logtalk for defining and using components?
- What support is provided in Logtalk for reflective programming?
- Using compiler options on calls to the Logtalk compiling and loading predicates do not work!
- Gecko-based browsers (e.g. Firefox) show non-rendered HTML entities when browsing XML documenting files!
- Compiling a source file results in errors or warnings but the Logtalk compiler reports a successful compilation with zero errors and zero warnings!
- Is Logtalk implemented as a meta-interpreter?
- What kind of code Logtalk generates when compiling objects? Dynamic code? Static code?
- How about message-sending performance? Does Logtalk use static binding or dynamic binding?
- Which Prolog-dependent factors are most crucial for good Logtalk performance?
- How does Logtalk performance compare with plain Prolog and with Prolog modules?
- Developer Tools
- Main files
- API documentation
- Writing, compiling, and loading unit tests
- Running unit tests
- Unit test dialects
- User-defined unit test dialects
- Skipping unit tests
- Testing non-deterministic predicates
- Testing generators
- Testing input/output predicates
- Suppressing tested predicates output
- Unit tests with timeout limits
- Setup and cleanup goals
- Test annotations
- Debugging failed unit tests
- Code coverage
- Automating running unit tests
- Utility predicates
- Exporting unit test results in xUnit XML format
- Exporting unit test results in the TAP output format
- Exporting code coverage results in XML format
- Known issues
- Other notes