|
Check-in Number:
|
4308 | |
| Date: |
2001-Aug-09 17:35:23 (local)
2001-Aug-09 15:35:23 (UTC) |
| User: | simons |
| Branch: | |
| Comment: |
Made the "xds_int-something" section more clear. |
| Tickets: |
|
| Inspections: |
|
| Files: |
|
ossp-pkg/xds/docs/libxds.tex 1.13 -> 1.14
--- libxds.tex 2001/08/09 15:29:58 1.13
+++ libxds.tex 2001/08/09 15:35:23 1.14
@@ -1,6 +1,6 @@
% -*- mode: LaTeX; fill-column: 75; -*-
%
-% $Id: libxds.tex,v 1.13 2001/08/09 15:29:58 simons Exp $
+% $Id: libxds.tex,v 1.14 2001/08/09 15:35:23 simons Exp $
%
\documentclass[a4paper,10pt,pointlessnumbers,bibtotoc]{scrartcl}
\usepackage[dvips,xdvi]{graphicx}
@@ -1076,7 +1076,8 @@
names of these data types vary from vendor to vendor. To solve that, we
defined our own data types. The application programmer might want to take a
look at the top few lines of the \textsf{xds.h} include file to see how the
-actual data types are mapped to the \textsf{xds\_xxx\_t} variant.
+actual data types are mapped to the \textsf{xds\_xxx\_t} variant on your
+system.
\subsection{Why do I have to register all the engines manually?}
|
|
