$Revision: 1.1.2.12 $
The index for the Allegro CL documentation is in index.htm.
This document provides an overview by subject of the Allegro CL documentation. There are numbered major headings. The numbers are for ease of reference in this document only (and do not appear in other documents). The numbering roughly follows the chapter numbers in the Allegro CL 4.3 User Guide. Where one HTML document describes all the functionality of the heading, the whole heading is a link to that document. Where the information is spread over several HTML documents, each document name appears in the heading and is linked to the document it names. Under each major numbered heading is the list of headings in the document. (Notice that each document uses numbering starting at 1.0.)
These documents do not appear in these contents: aclwffi.htm, aclwin.htm, ffi43com.htm, iacl.htm, ole.htm, plugin.htm, release_notes.htm, and runtime.htm.
Here are the major headings in this document (they are linked to their locations below in this document):
1 Introduction (introduction.htm)
2 Starting and running Lisp (startup.htm)
3 Implementation and extensions
4 The top-level (top_level.htm)
5 The debugger (debugging.htm)
6 The inspector (inspector.htm)
7 Compiling (compiling.htm) and loading (loading.htm) functions
8 Operating-system interface (os_interface.htm) and dumplisp (dumplisp.htm)
9 Flavors (flavors.htm)
10 Foreign functions (foreign_functions.htm) and foreign types (ftype.htm)
11 Profiling (profiling.htm)
12 Multiprocessing: stack-groups, processes and locks (multiprocessing.htm)
13 Advice (advice.htm), regular expression support (regexp.htm) and miscellaneous functionality (miscellaneous.htm)
14 The Emacs-Lisp interface
15 Garbage collection (gc.htm)
16 Defsystem (defsystem.htm)
17 Source-file recording (source_file_recording.htm) and cross referencer (cross_reference.htm)
18 The implementation of streams (streams.htm)
19 Building images (building_images.htm) and delivery (delivery.htm)
20 Errors (errors.htm)
21 Sockets (socket.htm)
22 Allegro ODBC (aodbc_v2.htm)
23 International Allegro CL (iacl.htm)
1.0 Documentation introduction
1.2 Some notation
2.0 The Overview section
2.1 Contents of Allegro CL documentation
2.2 List of HTML overview documents
3.0 The Reference section
4.0 Assistance available on the internet and the World Wide Web
4.1 The Allegro CL FAQ
4.2 Patches
4.3 Further information
4.4 Should you get all patches?
5.0 Reporting bugs
5.1 Where to report bugs and send questions
6.0 Common Graphics and Integrated Development Environment documentation [Windows only]
1.0 The Allegro directory
2.0 Starting Allegro CL
2.1 Starting on UNIX machines
2.2 Starting on Windows machines
2.3 The executable, the image, and additional files
2.4 The executable and image names
2.5 Argument defaults
3.0 Command line arguments
4.0 Files Lisp must find to start up and files it may need later
4.1 Files Lisp needs to start up 1: .so (or dll) files built with image
4.2 Files Lisp needs to start up 2: the Allegro directory
5.0 The start-up message
6.0 Running Lisp as a subprocess of Emacs
6.1 Starting Lisp as a subprocess of Emacs the first time
6.2 Starting Lisp within Emacs after the first time
6.3 What if the Emacs-Lisp interface does not start?
6.4 Using the IDE with Emacs
7.0 Starting Lisp from a shell
8.0 Start-up problems
9.0 How to exit Lisp
9.1 How to exit for sure
10.0 What Lisp does when it starts up
11.0 Initialization and the sys:siteinit.cl and [.]clinit.cl files
11.1 Errors in an initialization file
11.2 No top-level commands in initialization files
11.3 Cannot (effectively) set a variable bound by load
11.4 Starting Allegro Composer from .clinit.cl
12.0 Setting global variables in initialization files
12.1 Where are the bindings defined?
12.2 Many bindings are to specific values, not to the variables' actual value
12.3 How to set the value so a listener sees it?
12.4 A sample initialization file
13.0 After Lisp starts up
13.1 The initial prompt
13.2 Errors
13.3 What if the system seems to hang?
13.4 Enough C-c's (on Unix) will always interrupt
13.5 The Allegro Icon on the system tray will interrupt on Windows
13.6 Help while running Lisp
14.0 Files that may be looked for on startup and after startup
Some of this information is in implementation.htm but pathnames are discussed in pathnames.htm and packages in packages.htm. See also case.htm which describes case modes in Allegro CL (its contents are below as well).
The contents of implementation.htm are:
1.0 Implementation introduction
2.0 Data types
3.0 Characters
4.0 Autoloading
4.1 Where the autoloaded files are located
4.2 Common Lisp symbols
4.3 Major extensions
4.4 How to load modules
5.0 Miscellaneous implementation details
5.1 Extensions to cl:make-package, cl:disassemble, cl:open
5.2 cl:directory
5.3 Reader macros and cl:*features*
5.4 cl:random
5.5 cl:make-hash-table
5.6 cl:make-array
6.0 Allegro CL and the ANSI CL standard
6.1 Compatibility with pre-ANSI CLtL-1 in Allegro CL
6.2 Other package changes and compile-time-too behavior
6.3 The function data type
6.4 CLOS and MOP
6.5 CLOS and MOP conformance
6.6 CLOS optimization
7.0 Function specs
8.0 Some low-level functionality
Windows: GetWinMainArgs2
9.0 Compliance with the ANSI specification
The contents of pathnames.htm are:
1.0 Unix symbolic links and truenames
2.0 Windows devices
3.0 Parsing Unix pathnames3.1 Preprocessing
3.2 Determining the directory component
3.3 Determining the name component
3.4 Determining the type component
3.5 Anomalies
3.6 Table of examples4.0 The directory component of merged pathnames
5.0 Parsing Windows pathnames
6.0 Logical pathnames6.1 Logical pathnames: introduction
6.2 Logical pathnames: general implementation details
6.3 Logical pathanmes: some points to note
6.4 Details of cl:load-logical-pathname-translations
The contents of packages.htm are:
1.0 Packages introduction
2.0 Packages in Allegro CL
3.0 Notes on specific packages
4.0 Package nicknames
5.0 Package locking and package definition locking
5.1 Package locking
5.2 Package definition locking
5.3 Implementation packages
5.4 Package locked errors
5.5 Locally circumventing package locked errors
5.6 Package locked by default
5.7 Justification for package lockingThe contents of case.htm are:
1.0 Introduction to case in Allegro CL
2.0 The Modes
3.0 readtable-case
4.0 The cost of portability
5.0 Portability
5.1 Package names
5.2 Package definitions
5.3 Creating symbols
5.4 Testing symbols
6.0 Importing Upper Case code into Lower Case mode
1.0 Introduction to the Lisp top-level listener
2.0 The prompt
3.0 Commands and expressions
3.1 Case sensitivity of input
3.2 Getting help for top-level commands
3.3 Command and expression history
3.4 Anomalies with the :history list
4.0 Break levels
4.1 Commands to manipulate break levels:
5.0 Commands for compiling and loading
5.1 File arguments are read as strings
6.0 Top-level interaction with multiprocessing
7.0 Commands for killing processes and exiting Lisp
8.0 Miscellaneous top-level commands
9.0 Top-level variables
10.0 Adding new top-level commands
1.0 Introduction
2.0 Getting out of the debugger
3.0 Internal functions
4.0 Debugging background processes
5.0 Stack commands
5.1 :zoom
5.2 :brief, :moderate, and :verbose modes of :zoom
5.3 :all t and :all nil modes of :zoom
5.4 :function t and :function nil modes of :zoom
5.5 :specials t and :specials nil modes of :zoom
5.6 :relative t and :relative nil modes of :zoom
5.7 The :bt command for a quick look at the stack
5.8 Variables that affect the behavior of :zoom
5.9 Special handling of certain errors by :zoom
5.10 :zoom analogs and stack movement commands
5.11 Commands that hide frames
5.12 Frame information commands
5.13 Local variables and evaluation
5.14 Getting a backtrace programmatically
6.0 Local variables and the debugger
6.1 Discard local variable information before dumplisp
6.2 Summary of the discussion of locals
6.3 What are local variables?
6.4 How does the compiler treat local variables?
6.5 What is the difference between using registers and using the stack?
6.6 Live and dead ranges of local variables
6.7 Locals and functions in the tail position
6.8 Example showing live range
6.9 The debug=1 behavior with locals
6.10 The behavior with debug=2
6.11 Problem with debug=1 and debug=2 behavior before a local has a value
6.12 Why only have good behavior of locals at debug=3?
6.13 The behavior with debug=3 (and speed < 3)
6.14 The behavior with debug=3 and speed=3
6.15 I compiled with debug=3 but I want to see dead locals anyway
7.0 Break on exit
8.0 :return and :restart
9.0 Ghost frames in backtraces
9.1 Summary of the ghost frames section
9.2 What is a ghost frame?
9.3 What kinds of optimizations cause ghost frames?
9.4 How does the debugger know about ghost frames?
9.5 When will the debugger display ghost frames?
9.6 Can I return from or restart a ghost frame?
9.7 What do the suspension points (`...') mean in a ghost frame?
9.8 The ghost frame has no `...'s; are all possible frames displayed?
9.9 No ghost frames are displayed. Do all functions appear on the stack?
9.10 Ghost frames in a brief backtrace
9.11 Can I turn off printing of ghost frames?
9.12 Can backtraces involving system functions have ghost frames?
9.13 Ghost frames and Allegro Composer
10.0 The tracer
10.1 Trace example
10.2 Tracing setf, :before, and :after methods
11.0 The stepper
11.1 Turning stepping off
11.2 Other stepping commands and variables
11.3 Stepping example
12.0 The Lisp DeBug (ldb) stepper
12.1 Entering and Exiting the ldb stepper
12.2 Ldb stepper functional interface
12.3 Ldb stepping example run
1.0 The inspector introduction
2.0 Inspect commands
3.0 An example of inspect
The contents of compiling.htm are:
1.0 Lisp images without a compiler
2.0 Compile-file
3.0 No-in-package warning
4.0 Undefined function warning
5.0 EOF encountered error
6.0 Variables which control information printed by compile-file
7.0 File types
8.0 Declarations and optimizations8.1 Examining the current settings and their effect
8.2 Declared fixnums example
8.3 Argument count checking example
8.4 Argument type for a specialized function example
8.5 Bound symbol example
8.6 Tail merging discussion
8.7 Changing compiler optimization switch settings
8.8 Switch can be t or nil meaning always on or always off9.0 Pointers for choosing speed and safety values
9.1 Optimizing for fast floating-point operations
9.2 Supported operations
9.3 Help with declarations
9.4 Explain types and calls
9.5 Explain boxing
9.6 Explain variables10.0 Other declarations and optimizations
10.1 Inline declarations ignored
10.2 Defstruct accessors
10.3 Stack consing and allocation
10.4 Adding typep-transformers
10.5 Compiler handling of top-level forms
The contents of loading.htm are:
1.0 Using the load function
1.1 EOF encountered error during a load
1.2 Special utilities for loading applications
2.0 Search lists
2.1 Search List Structure
2.2 Search lists variables
2.3 Search list example
3.0 The Allegro Presto algorithm
3.1 Comparison to autoloading
3.2 Improved locality of reference
3.3 Allegro Presto: basic usage
3.4 Allegro Presto: advanced usage
3.5 Libfasl loading
3.6 What does the libfasl feature apply to?
3.7 What does the libfasl feature do?
3.8 When is a stub function fully loaded?
3.9 When is libfasl loading invoked?
3.10 What are the costs and advantages of using the libfasl feature?
3.11 The in-package restriction
3.12 Affect on users 1: keeping track of files
3.13 What happens if Lisp cannot find a necessary fasl file?
3.14 What happens if the file has changed?
3.15 Affect on users 2: eq-ness of function objects
3.16 Libfasl and excl:dumplisp
User-defined main (main.htm), which describes how to provide your own main() on Unix and on Windows, and sigio-handling (see the page description of set-sigio-handler) were also in chapter 8 in the 4.3 User Guide.
The contents of os_interface.htm are:
1.0 Operating-system interface
2.0 Subprocess functions
3.0 Environment functions
4.0 Temporary directory and files
5.0 Accessing command-line arguments
6.0 Polling and setting environment variablesThe contents of dumplisp.htm are:
1.0 Introduction to excl:dumplisp
2.0 Changes from earlier releases
3.0 Finding additional files
4.0 Uses of excl:dumplisp
5.0 excl:dumplisp will fail under some conditions
6.0 <allegro directory>/code/aclstart.cl is the source code for startup
7.0 Creating an application
8.0 Creating a customized image
9.0 When the dumped image starts 1: values of global variables
10.0 When the dumped image starts 2: command-line arguments
11.0 When the dumped image starts 3: reading init files
12.0 When the dumped image starts 4: restart actions
13.0 When the dumped image starts 5: the two restart functions
14.0 The emacs-lisp interface and dumped images
15.0 Dumping a prestoized image
16.0 Standalone image: not supported
17.0 How the dumped image finds loaded library files
18.0 Logical pathnames and the dumped image
19.0 How the dumped image finds its Allegro directory
20.0 How to use the dumped image
Flavors is supported for backward compatibility only. See the flavors.htm file for contents.
Users porting from Allegro CL 4.3.x (mostly on Unix machines) see also ffi43com.htm. Users porting from Allegro CL 3.0.2 see also aclwffi.htm.
The contents of foreign_functions.htm are:
1.0 Foreign functions introduction
1.1 Some notation
1.2 Different versions of Allegro CL load foreign code differently
1.3 Package information
1.4 Load foreign code with cl:load
1.4.1 Foreign File Processing
1.4.2 Externals must be resolved when the .so/.sl/.dll file is created
1.4.3 One library file cannot depend on an already loaded library file
1.4.4 Entry points are updated automatically
1.4.5 Duplicate entry points are never a problem
1.4.6 If you modify a so/sl/dll file that has been loaded, you must load the modified file!
1.5 Foreign code cannot easily be included at installation time
1.6 Foreign functions and multiprocessing
1.7 Creating Shared Objects that refer to ACL Functionality
2.0 The 4.3.x UNIX model for foreign functions
3.0 The ACL 3.0.x for Windows model for foreign functions
4.0 The 5.0 foreign function interface specification
4.1 Foreign function interface function summary
4.1.1 A note on foreign addresses
4.2 def-foreign-call
4.2.1 def-foreign-call syntax
4.2.2 def-foreign-call examples
4.3 def-foreign-variable
4.3.2 def-foreign-variable examples
5.0 Conventions for passing arguments
5.1 Modifying arguments called by address: use arrays
5.2 Lisp may not see a modification of an argument passed by address
5.3 Lisp unexpectedly sees a change to an argument passed by address
5.4 Passing fixnums, bignums, and integers
5.5 Another example using arrays to pass values
6.0 Passing strings between Lisp and C
6.1 Passing strings from Lisp to C
6.2 Special Case: Passing an array of strings from Lisp to C
7.0 Handling signals in foreign code
8.0 Input/output in foreign code
9.0 Using Lisp functions and values from C
9.1 Accessing Lisp values from C: lisp_value()
9.2 Calling Lisp functions from C: lisp_call_address() and lisp_call()
9.3 Calling foreign callables from Lisp
Appendix A: Foreign Functions on Windows
A.1 Making a .dll
A.2 Making a Fortran .dll
A.3 The Lisp side of foreign functions
A.4 A complete example
Appendix B: building shared libraries on Solaris 2.4 or later
Appendix C: building shared libraries on HP-UX 10.20
Appendix D: building shared libraries on SGI/IRIX 6.2 or later
Appendix E: building shared libraries on Dec Unix 4.0 or later
Appendix F: building shared libraries on AIX 4.2 or later
Appendix G: building shared libraries on Linux
Appendix H: building shared libraries on FreeBSD
The contents of ftype.htm are:
1.0 Foreign types introduction
2.0 The foreign types facility
3.0 Examples
4.0 The Syntax for Foreign Types
5.0 Primitive Types
6.0 Allocation types
7.0 Aligned Pointers
8.0 Bit Fields
9.0 The Programming Interface
10.0 Passing Foreign Objects to Foreign Functions
1.0 The three profilers: general information
1.1 The time profiler
1.2 The space profiler
1.3 The call-counting profiler
2.0 Invoking the profiler
3.0 Further points, including information on temporary files
4.0 Controlling the operation of the profiler
4.1 Control of data collection
4.2 Profiling with multiprocessing enabled
4.3 Closures in profiler output
5.0 Interpreting the results
5.1 Call-count results
5.2 Space and time profiler results
5.3 Examples
1.0 Multiprocessing introduction
1.1 Data types added to standard Common Lisp
1.2 stack-groups (non :os-threads model)
2.0 Processes and profiling (both models)
3.0 :os-threads model thread-related variables and functions
3.1 Threads and processes in the :os-threads model
3.2 The :os-threads model and foreign functions (:os-threads model)
3.3 Waiting for input from a stream (:os-threads model)
3.3.1 mp:process-wait vs mp:wait-for-input-available (:os-threads model)
4.0 Stack-group variables and functions in the non :os-threads model
4.1 Stack-group programming example (non :os-threads model)
4.2 Processes in the non :os-threads model
4.3 Waiting for input from a stream (non :os-threads model)
4.3.1 mp:process-wait vs mp:wait-for-input-available (non :os-threads model)
5.0 Process functions and variables (both models)
6.0 Processes and their dynamic environments (both models)
6.1 Lisp listeners and special variable bindings
7.0 Process locks (both models)
8.0 A simple example of multiprocessing
regexp.htm, which describes regular expression support in Allegro CL, has no subsections.
The contents of advice.htm are:
1.0 Introduction
2.0 Advising a function
2.1 Advice of class :before
2.2 Advice of class :around
2.3 Advice of class :after
3.0 Removing advice from a function or macro
4.0 Utilities associated with advice
5.0 Examples using advice
6.0 Advising macros
The contents of miscellaneous.htm are:
1.0 Introduction
2.0 The fasl reader/writer
3.0 Miscellaneous extensions
4.0 Creating and using pll files
The emacs-lisp interface is described in <Allegro directory>/eli/readme.htm. We do not put its contents here.
1.0 Garbage collection introduction
1.1 The garbage collection scheme
1.2 How newspace is managed with scavenges
1.3 The system knows the age of objects in newspace
1.4 Objects that survive long enough are tenured to oldspace
1.5 Placement of newspace and oldspace: the simple model
1.6 Oldspace, newspace, and Lisp will grow when necessary
1.7 The almost former gap problem
2.0 User control over the garbage collector
2.1 Switches and parameters
2.2 Triggering a scavenge
2.3 Triggering a global gc
2.4 Getting information on memory management
3.0 Tuning the garbage collector
3.1 How do I find out when scavenges happen?
3.2 How many bytes are being tenured?
3.3 When there is a global gc, how many bytes are freed up?
3.4 How many old areas are there after your application is loaded?
3.5 Can other things be changed while running?
4.0 Initial sizes of old and new spaces
5.0 System parameters and switches
5.1 Parameters that control generations and tenuring
5.2 Parameters that control minimum size
5.3 Parameters that control how big newly allocated spaces are
5.4 Gsgc switches
5.5 Gsgc functions and variables
6.0 Global garbage collection
6.1 The tenuring macro
7.0 Gc cursors
8.0 Other gc information
9.0 gc errors
9.1 Storage-condition errors
10.0 Weak vectors, finalizations, static arrays, etc.
10.1 Weak vectors and hashtables
10.2 Finalizations
10.3 Example of weak vectors and finalizations
10.4 Static arrays
1.0 Defsystem introduction
1.1 Defsystem terminology
2.0 Using Defsystem
3.0 Module-specifications
3.1 Short form module-specifications
3.2 Long form module-specifications
4.0 Redefinition of systems
5.0 Predefined operations on systems and defsystem variables
6.0 Extending Defsystem
6.1 Class hierarchy
6.2 Defining new classes
7.0 Extending defsystem syntax through shared-initialize methods
7.1 Defsystem methods that can be specialized
8.0 Defsystem extension examples
8.1 Example of defining a new system class
8.2 Example of defining new system operations
8.3 Example of master and development directories
8.4 Example of one system definition referencing another
The contents of source_file_recording.htm are:
1.0 Source-file recording Introduction
2.0 Redefinition warnings
2.1 Pathname comparisonThe contents of cross_reference.htm are:
1.0 Cross reference introduction
1.1 The cross-reference package
1.2 The cross-reference database
1.3 When is the cross-reference information generated?
1.4 When is xref information in a fasl file added to the database?
1.5 Things to note about the compiler and macros
2.0 What is in and how to access the xref database
2.1 Clearing the database
2.2 General description of query functions and commands
2.3 The function-name and object arguments
2.4 File information and the :in-files keyword argument
2.5 The :in-functions keyword argument
2.6 The :inverse keyword argument
3.0 A cross-referencer example
1.0 Introduction to streams in Allegro CL
2.0 Documenting object-oriented protocols
3.0 Stream classes
4.0 Generic functions for character input
5.0 Generic functions for character output
6.0 Generic functions for binary streams
7.0 Functions for efficient input and output of sequences
8.0 Creating streams
9.0 Miscellaneous stream functions
The contents of building_images.htm are:
1.0 Comparison with earlier releases
2.0 Comparison with excl:dumplisp
3.0 Comparison with excl:generate-application
4.0 The template of a call to build-lisp-image
5.0 Arguments to build-lisp-image 1: defaults inherited from the running image
6.0 Arguments to build-lisp-image 2: defaults not inherited from running image
7.0 Use of custom.cl
8.0 Building an image to include patches
9.0 Comparison of build-lisp-image with version 4.3's build/install_lisp
10.0 Minimal top levels
10.1 Using the default minimal top-level
10.2 Requiring the normal top-level in a minimal top-level lisp
10.3. Top-level variablesThe contents of delivery.htm are:
1.0 Delivery introduction
2.0 Definitions
3.0 Developing the application and preparing for delivery
3.1 A summary of the delivery process
3.2 Legal and licensing issues
3.3 Deciding on necessary features
3.4 Deciding on top-level (user interaction)
3.5 Packaging the product
3.6 Including all desired modules
3.7 Defining the init functionality
3.8 Specifying the initial value of *package*
3.9 Setting up logical pathname translations
3.10 Use of shared libraries (foreign files)
3.11 CLOS training
3.11.1 Generic functions, method combination, and discrimination
3.11.2 Effective methods
3.11.3 Caches for fast dispatching
3.11.4 Constructor functions
3.11.5 How to do CLOS start up optimizations
3.11.6 make-instance optimization
4.0 Creating the deliverable
4.1 Resources
4.2 Defsystem
4.3 Tuning the application
4.4 More on the development environment
4.5 GC parameters and switches
4.6 GC cursors
4.7 Allegro Presto
4.8 Allegro Runtime
4.9 Windows specific information
5.0 Patching your application after delivery
5.1 The Allegro CL patch naming scheme
5.2 Loading Allegro CL patches
5.3 Patches for your application
5.4 Creating patch files in general
5.5 Creating a patch file
5.6 What to do with patch files
5.7 Including application patches in an image at build time
5.8 Superseding a patch
5.9 Withdrawing a patch
5.10 Distributing patches
5.11 Loading patches
1.0 Errors
2.0 Some common errors
2.1 An unhandled error occurred during initialization: <message>
2.2 Attempt to call <name> which is defined as a macro
2.3 Gc errors
2.4 Bus errors and segmentation violations
2.5 Using package <package> results in name conflicts...
1.0 Introduction and background
2.0 Characteristics
3.0 Stream Sockets
3.1 Connections
3.2 Host Naming
4.0 Variables
5.0 Functions
6.0 Errors
7.0 Examples
This document describes the new (in version 5.0.1) Allegro ODBC interface. Note that AODBC version 1 is not documented online and is incompatible with version 2. Further note that the functionality is not licensed to all customers. If you wish a license and do not have one, please contact you Franz Inc. sales representative. See the Add On Products table in readme.htm for information on availability and licensing of AODBC, version 2.
1.0 Introduction
1.1 Platform-specific information
2.0 What has changed since version 1.0
3.0 Using ODBC
4.0 ODBC examples
4.1 A simple interaction
4.2 binding input parameters
4.3 scanning through rows
5.0 Character input buffers
6.0 Queries
7.0 Reference
8.0 Conditions
This document describes International Allegro CL (IACL), the version that supports various charcater sets beyond ASCII. interface. Note that IACL is not licensed to all customers. If you wish a license and do not have one, please contact you Franz Inc. sales representative.
1.0 Introduction
2.0 Quick guide to changes
2.1 Differences between International and standard Allegro CL
2.2 New in release 5.0.1
3.0 Encoding for extended character sets
3.1 Extended UNIX Code or EUC
3.2 JIS
3.3 Shift-JIS
3.4 Process code or Fat
4.0 Changes to standard Lisp caused by fat character representation
4.1 Reading and writing files in International Allegro CL
4.1.2 Stream external formats and the open function
4.2 Character functions applied to extended characters
5.0 Foreign functions
5.1 Example 1: Foreign function expects EUC string
5.2 Example 2: Foreign function expects Process-Code string
5.3 Functions that support passing strings to and from foreign code
6.0 Miscellaneous and known problems
6.1.1 Known problems
7.0 Installation
Index
Copyright (C) 1998-1999, Franz Inc., Berkeley, CA. All Rights Reserved.