paweld/fpc
1
0
Fork 0
mirror of https://gitlab.com/freepascal.org/fpc/source.git synced 2025-12-06 10:07:14 +01:00
Code Issues Packages Projects Releases Wiki Activity

* fixes for latex2html 0.99b2

Browse Source
This commit is contained in:
peter 2000-07-11 18:07:26 +00:00
parent 7320410b6b
commit 048b6fa475
10 changed files with 523 additions and 472 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
docs/Makefile
View File

@ -161,9 +161,9 @@ help:
@echo ' pdfdist : pdf, and archive result.'
clean:
-rm -rf $(HTML)
-rm -rf $(HTML) onechap
-rm -f $(TOC) $(LOG) $(DVI) $(PDF) $(AUX) $(OUT) $(PS) *.i* $(LOT) $(TXT) $(CHK)
-rm -f onechap.dvi onechap.aux onechap.log
-rm -f onechap.dvi onechap.aux onechap.log onechap.chk
# Units
-$(MAKE) -C crtex clean
@ -330,6 +330,22 @@ else
endif
touch internal.chk
onechap: onechap.chk
onechap.chk: onechap.tex date.inc
ifdef INSTALLDEBUG
mkdir onechap
cp onechap.tex onechap/index.html
else
$(LATEX2HTML) $(LATEX2HTMLOPTS) -split 4 -link 2\
-t "Free Pascal reference guide" onechap.tex
-sed -f foot.sed <onechap/footnode.html >onechap/footnote.html
-mv onechap/footnote.html onechap/footnode.html
-rm -f onechap/labels.pl onechap/internals.pl onechap/.*.pag onechap/.*.dir
-rm -f onechap/images.* onechap/*.log onechap/WARNINGS
endif
touch onechap.chk
html: $(HTML)
#####################################################################
@ -444,7 +460,10 @@ linuxexamples: examples
#
# $Log$
# Revision 1.39 2000-07-09 15:44:15 peter
# Revision 1.40 2000-07-11 18:07:26 peter
# * fixes for latex2html 0.99b2
#
# Revision 1.39 2000/07/09 15:44:15 peter
# * image_type gif added
#
# Revision 1.38 2000/07/04 21:23:04 michael

11
docs/fpc-html.tex
View File

@ -46,6 +46,15 @@
\newcommand{\seeo}[1]{See \htmlref{#1}{option:#1}}
\newcommand{\seet}[1]{table (\htmlref{#1}{tab:#1}) }
%
% Function list
%
\newenvironment{funclist}{\begin{list}}{\end{list}}
\newcommand{\funcrefl}[3]{\item[\htmlref{#2}{fu:#2} #3]}
\newcommand{\funcref}[2]{\item[\htmlref{#1}{fu:#1} #2]}
\newcommand{\procrefl}[3]{\item[\htmlref{#2}{pro:#2} #3]}
\newcommand{\procref}[2]{\item[\htmlref{#1}{pro:#1} #2]}
%
% Function/procedure environments
%
@ -113,7 +122,7 @@
%
% Some versions
%
\newcommand{\fpcversion}{0.99.12}
\newcommand{\fpcversion}{1.00.0}
%
% PDF support

14
docs/fpc.sty
View File

@ -186,15 +186,14 @@
%
% PDF support
%
\latex{%
\newif\ifpdf
\ifx\pdfoutput\undefined
\newif\ifpdf
\ifx\pdfoutput\undefined
\pdffalse
\else
\else
\pdfoutput=1
\pdftrue
\fi
}
\fi
%
% For examples
%
@ -215,6 +214,7 @@
\par
\raisebox{-1em}{\makebox[\textwidth]{Name\hfill Description \hfill Page}}\\
\rule{\textwidth}{1pt}
\html{Name\hfill Description \hfill Page}
\begin{list}{}{%
\setlength{\rightmargin}{0pt}\setlength{\topsep}{0cm}\setlength{\partopsep}{0pt}%
\setlength{\itemsep}{0pt}\setlength{\labelwidth}{3.5cm}%
@ -260,5 +260,7 @@
\pdfpagewidth=210mm
\pdfpageheight=297mm
\fi
\usepackage{html}
\usepackage{htmllist}
%
% end of fpc.sty

13
docs/heaptrc.tex
View File

@ -89,14 +89,14 @@ has no debug info included.
The \var{FillExtraInfoType} is a procedural type used in the
\seep{SetExtraInfo} call.
\begin{lstlisting}{}
\begin{verbatim}
type
FillExtraInfoType = procedure(p : pointer);
\end{lstlisting}{}
\end{verbatim}
The following typed constants allow to fine-tune the standard dump of the
memory usage by \seep{DumpHeap}:
\begin{lstlisting}{}
\begin{verbatim}
const
tracesize = 8;
quicktrace : boolean = true;
@ -104,7 +104,7 @@ const
keepreleased : boolean = false;
add_tail : boolean = true;
usecrc : boolean = true
\end{lstlisting}{}
\end{verbatim}
\var{Tracesize} specifies how many levels of calls are displayed of the
call stack during the memory dump. If you specify \var{keepreleased:=True}
@ -206,7 +206,10 @@ trace.
%
% $Log$
% Revision 1.5 2000-05-16 21:07:55 michael
% Revision 1.6 2000-07-11 18:07:26 peter
% * fixes for latex2html 0.99b2
%
% Revision 1.5 2000/05/16 21:07:55 michael
% + Implemented large part of TODO list. Too much to denote
%
% Revision 1.4 2000/02/07 11:21:06 michael

6
docs/internal.tex
View File

@ -26,11 +26,13 @@
\usepackage{xspace}
\usepackage{a4dutch}
\usepackage{makeidx}
\usepackage{html}
\usepackage{htmllist}
\usepackage{fancyheadings}
\usepackage{epsfig}
\usepackage{multicol}
\ifx\pdfoutput\undefined
\usepackage{html}
\usepackage{htmllist}
\fi
\usepackage{fpc}
\latex{%
\ifpdf

13
docs/onechap.tex
View File

@ -21,10 +21,17 @@
\documentclass{report}
\usepackage{a4}
\usepackage{makeidx}
\usepackage{html}
\usepackage{times}
\ifx\pdfoutput\undefined
\usepackage{html}
\usepackage{htmllist}
\fi
\usepackage{fpc}
\latex{
\usepackage{listings}
\lstset{language=delphi}
}
\html{\input{fpc-html.tex}}
\begin{document}
%\input{crt.tex}
%\input{dos.tex}
@ -34,11 +41,11 @@
%\input{go32.tex}
%\input{gpm.tex}
%\input{graph.tex}
%\input{heaptrc.tex}
\input{heaptrc.tex}
%\input{ipc.tex}
%\input{ide.tex}
%\input{linux.tex}
\input{math.tex}
%\input{math.tex}
%\input{mmx.tex}
%\input{mouse.tex}
%\input{objects.tex}

6
docs/prog.tex
View File

@ -22,10 +22,12 @@
%
% Preamble
%
\usepackage{html}
\usepackage{htmllist}
\usepackage{epsfig}
\usepackage{multicol}
\ifx\pdfoutput\undefined
\usepackage{html}
\usepackage{htmllist}
\fi
\usepackage{fpc}
\latex{%
\ifpdf

46
docs/ref.tex
View File

@ -22,10 +22,12 @@
%
% Preamble
%
\usepackage{html}
\usepackage{htmllist}
\usepackage{epsfig}
\usepackage{multicol}
\ifx\pdfoutput\undefined
\usepackage{html}
\usepackage{htmllist}
\fi
\usepackage{fpc}
\latex{%
\ifpdf
@ -1866,14 +1868,14 @@ one. The \var{Inherited} keyword will not jump to the inherited method, if
virtual was used.
The following code is {\em wrong}:
\begin{lstlisting}{}
\begin{verbatim}
Type ObjParent = Class
Procedure MyProc; virtual;
end;
ObjChild = Class(ObjPArent)
Procedure MyProc; virtual;
end;
\end{lstlisting}{}
\end{verbatim}
The compiler will produce a warning:
\begin{verbatim}
Warning: An inherited method is hidden by OBJCHILD.MYPROC
@ -1882,14 +1884,14 @@ The compiler will compile it, but using \var{Inherited} can
produce strange effects.
The correct declaration is as follows:
\begin{lstlisting}{}
\begin{verbatim}
Type ObjParent = Class
Procedure MyProc; virtual;
end;
ObjChild = Class(ObjPArent)
Procedure MyProc; override;
end;
\end{lstlisting}{}
\end{verbatim}
This will compile and run without warnings or errors.
\subsection{Message methods}
@ -1902,9 +1904,9 @@ identifiers.
Message methods that are declared with an integer constant can take only one
var argument (typed or not):
\begin{lstlisting}{}
\begin{verbatim}
Procedure TMyObject.MyHandler(Var Msg); Message 1;
\end{lstlisting}{}
\end{verbatim}
The method implementation of a message function is no different from an
ordinary method. It is also possible to call a message method directly,
but you should not do this. Instead use the \var{TObject.Dispatch} method.
@ -1913,7 +1915,7 @@ The \var{TOBject.Dispatch} method can be used to call a \var{message}
handler. It is declared in the \file{system} unit and will accept a var
parameter which must have at the first position a cardinal with the
message ID that should be called. For example:
\begin{lstlisting}{}
\begin{verbatim}
Type
TMsg = Record
MSGID : Cardinal
@ -1922,7 +1924,7 @@ Var
Msg : TMSg;
MyObject.Dispatch (Msg);
\end{lstlisting}{}
\end{verbatim}
In this example, the \var{Dispatch} method will look at the object and all
it's ancestors (starting at the object, and searching up the class tree),
to see if a message method with message \var{MSGID} has been
@ -1933,15 +1935,15 @@ If no such method is found, \var{DefaultHandler} is called.
\var{DefaultHandler} is a virtual method of \var{TObject} that doesn't do
anything, but which can be overridden to provide any processing you might
need. \var{DefaultHandler} is declared as follows:
\begin{lstlisting}{}
\begin{verbatim}
procedure defaulthandler(var message);virtual;
\end{lstlisting}{}
\end{verbatim}
In addition to the message method with a \var{Integer} identifier,
\fpc also supports a messae method with a string identifier:
\begin{lstlisting}{}
\begin{verbatim}
Procedure TMyObject.MyStrHandler(Var Msg); Message 'OnClick';
\end{lstlisting}{}
\end{verbatim}
The working of the string message handler is the same as the ordinary
integer message handler:
@ -1950,7 +1952,7 @@ The \var{TOBject.DispatchStr} method can be used to call a \var{message}
handler. It is declared in the system unit and will accept one parameter
which must have at the first position a string with the message ID that
should be called. For example:
\begin{lstlisting}{}
\begin{verbatim}
Type
TMsg = Record
MsgStr : String[10]; // Arbitrary length up to 255 characters.
@ -1959,7 +1961,7 @@ Var
Msg : TMSg;
MyObject.DispatchStr (Msg);
\end{lstlisting}{}
\end{verbatim}
In this example, the \var{DispatchStr} method will look at the object and
all it's ancestors (starting at the object, and searching up the class tree),
to see if a message method with message \var{MsgStr} has been
@ -1970,15 +1972,15 @@ If no such method is found, \var{DefaultHandlerStr} is called.
\var{DefaultHandlerStr} is a virtual method of \var{TObject} that doesn't do
anything, but which can be overridden to provide any processing you might
need. \var{DefaultHandlerStr} is declared as follows:
\begin{lstlisting}{}
\begin{verbatim}
procedure DefaultHandlerStr(var message);virtual;
\end{lstlisting}{}
\end{verbatim}
In addition to this mechanism, a string message method accepts a \var{self}
parameter:
\begin{lstlisting}{}
\begin{verbatim}
TMyObject.StrMsgHandler(Data : Pointer; Self : TMyObject);Message 'OnClick';
\end{lstlisting}{}
\end{verbatim}
When encountering such a method, the compiler will generate code that loads
the \var{Self} parameter into the object instance pointer. The result of
this is that it is possible to pass \var{Self} as a parameter to such a
@ -4553,13 +4555,13 @@ Const
\end{verbatim}
Further, the following non processor specific general-purpose constants
are also defined:
\begin{lstlisting}{}
\begin{verbatim}
const
erroraddr : pointer = nil;
errorcode : word = 0;
{ max level in dumping on error }
max_frame_dump : word = 20;
\end{lstlisting}{}
\end{verbatim}
\begin{remark}
Processor specific global constants are named Testxxxx where xxxx
represents the processor number (such as Test8086, Test68000),

6
docs/units.tex
View File

@ -28,10 +28,12 @@
\usepackage{xspace}
\usepackage{a4}
\usepackage{makeidx}
\usepackage{html}
\usepackage{htmllist}
\usepackage{syntax}
\usepackage{fancyhdr}
\ifx\pdfoutput\undefined
\usepackage{html}
\usepackage{htmllist}
\fi
\usepackage{fpc}
\latex{\usepackage{multicol}}
\latex{%

7
docs/user.tex
View File

@ -22,12 +22,15 @@
%
% Preamble
%
\usepackage{html}
\usepackage{htmllist}
\usepackage{epsfig}
\usepackage{multicol}
\ifx\pdfoutput\undefined
\usepackage{html}
\usepackage{htmllist}
\fi
\usepackage{fpc}
\latex{%
\usepackage{times}
\ifpdf
\pdfinfo{/Author(Michael Van Canneyt)
/Title(Users' Guide)