+ too many changes to enumerate

docs/Makefile

@@ -45,8 +45,8 @@ endif
 
 # Ascii mode ? (i.e. no pics)
 ifndef ASCIIMODE
-ASCIIMODE=NO
+#ASCIIMODE=NO
-#ASCIIMODE=YES
+ASCIIMODE=YES
 endif
 
 # DVI to PS converter
@@ -124,11 +124,6 @@ endif
 	$(PDFLATEX) $*pdf
 	mv $*pdf.pdf $*.pdf
 
-$(TXT) : %.txt: %.dvi
-
-$(DVI) : %.dvi: %.tex
-
-$(PDF) : %.pdf: %.tex
 
 #####################################################################
 # Targets
@@ -148,7 +143,6 @@ help:
 	@echo ' htmldist      : html, and rchive result.'
 	@echo ' psdist        : ps, and archive result.'
 	@echo ' pdfdist       : pdf, and archive result.'
- 
 
 clean:
 	-rm -rf $(HTML)
@@ -166,6 +160,12 @@ clean:
 	-$(MAKE) -C stringex clean
 	-$(MAKE) -C refex clean
 
+$(TXT) : %.txt: %.dvi
+
+$(DVI) : %.dvi: %.tex
+
+$(PDF) : %.pdf: %.tex
+
 unitex.chk:
 	$(MAKE) -C crtex tex
 	$(MAKE) -C dosex tex
@@ -187,9 +187,16 @@ refex.chk:
 messages: 
 	msg2inc -TE ../compiler/errore.msg messages.tex
 
-units.dvi: units.tex $(CHAPTERS)
+date:
+	@echo \\date\{`date +'%B %Y'`\} >date.inc
 
-ref.dvi: ref.tex
+units.dvi: units.tex date.inc $(CHAPTERS)
+
+ref.dvi: ref.tex date.inc
+
+prog.dvi: prog.tex date.inc
+
+user.dvi: user.tex date.inc
 
 units.pdf: units.tex $(CHAPTERS)
 
@@ -207,7 +214,7 @@ all : dvi ps pdf txt html
 
 user: user.chk
 
-user.chk: user.tex userex.chk
+user.chk: user.tex 
 	$(LATEX2HTML) $(LATEX2HTMLOPTS) -split 2 -link 2\
          -t "User's guide for Free Pascal" user.tex
 	sed -f foot.sed <user/footnode.html >user/footnote.html
@@ -277,14 +284,13 @@ dvidist: dvi
 	zip docs-dvi $(DVI)
 
 htmldist: html
-	find . -name '*.html' >htmllist
+	find . -name '*.html' -or -name '*.gif' -or -name '*.css' >htmllist
-	find . -name '*.gif' >>htmllist
 	tar -czf fpcdoc.tar.gz --files-from=htmllist
 	rm -f htmllist
 
 htm: html
 	makehtm `find . -name '*.html'`
-	zip -q doc-htm `find . -name '*.htm'` `find . -name '*.gif'`
+	zip -q docs-htm `find . -name '*.htm' -or -name '*.gif' -or -name '*.css'`
 	rm `find -name '*.htm'`
 	
 htmdist: htm
@@ -320,7 +326,10 @@ linuxexamples: examples
 
 #
 # $Log$
-# Revision 1.14  1998-10-01 12:57:22  michael
+# Revision 1.15  1998-11-17 23:42:02  michael
+# + too many changes to enumerate
+#
+# Revision 1.14  1998/10/01 12:57:22  michael
 # + Correction in dependencies
 #
 # Revision 1.13  1998/09/13 19:26:13  michael

docs/dos.tex

@@ -540,7 +540,7 @@ Under \linux the call exists, but is not implemented, i.e. it does nothing.}
 {\seep{GetFAttr}}
 
 \procedure{SetFTime}{(var F; Time: longint)}{
-\var{GetFTime} returns the modification time of a file,
+\var{SetFTime} sets the modification time of a file,
 this time is encoded and must be encoded with \var{PackTime}. 
 \var{F} must be a file type, which has been assigned, and
 opened.}{Errors are reported in \var{DosError}}

docs/prog.tex

@@ -35,7 +35,7 @@
 \title{Free Pascal \\ Programmers' manual}
 \docdescription{Programmers' manual for \fpc, version \fpcversion}
 \docversion{1.5}
-\date{September 1998}
+\input{date.inc}
 \author{Micha\"el Van Canneyt}
 \maketitle
 \tableofcontents
@@ -3578,7 +3578,7 @@ some limitations to the compiler:
 \begin{enumerate}
 \item Procedure or Function definitions can be nested to a level of 32.
 \item Maximally 255 units can be used in a program when using the real-mode
-compiler. When using the 32-bit compiler, the limit is set to 1024. You can
+compiler (i.e. a binary that was compiled by Borland Pascal). When using the 32-bit compiler, the limit is set to 1024. You can
 change this by redefining the \var{maxunits} constant in the 
 \file{files.pas} compiler source file.
 \end{enumerate}

docs/ref.tex

@@ -47,7 +47,7 @@
 \title{Free Pascal :\\ Reference guide.}
 \docdescription{Reference guide for Free Pascal.}
 \docversion{1.4}
-\date{March 1998}
+\input{date.inc}
 \author{Micha\"el Van Canneyt
 % \\ Florian Kl\"ampfl
 }

docs/units.tex

@@ -42,7 +42,7 @@
 \title{Free Pascal supplied units : \\ Reference guide.}
 \docdescription{Reference guide for standard Free Pascal units.}
 \docversion{1.3}
-\date{March 1998}
+\input{date.inc}
 \author{Micha\"el Van Canneyt\\ Florian Kl\"ampfl}
 \maketitle
 \tableofcontents

docs/user.tex

@@ -37,7 +37,7 @@
 \title{Free Pascal :\\ Users' manual}
 \docdescription{Users' manual for \fpc, version \fpcversion}
 \docversion{1.2}
-\date{March 1998}
+\input{date.inc}
 \author{Micha\"el Van Canneyt\\Florian Kl\"ampfl}
 \maketitle
 \tableofcontents
@@ -1419,6 +1419,11 @@ begin
 {...}
 end;
 \end{verbatim}
+(The \seeo{So} switch disables overloading. When you use it, the above will
+compile, as in Turbo Pascal.
+\item Operator overloading. \fpc allows to overload operators, i.e. you can
+define e.g. the '+' operator for matrices.
+\item On FAT16 and FAT32 systems, long file names are supported.
 \end{enumerate}
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
@@ -1431,7 +1436,9 @@ attempt to mimic the Turbo Pascal compiler in the following ways:
 the differences between Turbo Pascal and \fpc is that the latter requires
 you to specify an address operator when assigning a value to a procedural
 variable. In Turbo Pascal compatibility mode, this is not required.
-\item Procedure overloading is disabled.
+\item Procedure overloading is disabled. This means that function header and
+implementation can be different (i.e. the function iplementation doesn't
+need to repeat the function header).
 \item Forward defined procedures don't need the full parameter list when
 they are defined. Due to the procedure overloading feature of \fpc, you must
 always specify the parameter list of a function when you define it, even
@@ -1811,7 +1818,11 @@ function in \var{gdb}.
 The appendix {\ref{ch:GdbIniFile}} contains a sample init file for
 \var{gdb}, which produces good results when debugging \fpc programs.
 
+It is also possible to use \file{RHIDE}, a text-based IDE that uses gdb.
+There is a version of RHIDE available that can work together with FPC.
+
 \section{Caveats when debugging with \var{gdb}}
+
 There are some peculiarities of \fpc which you should be aware of when using
 \var{gdb}. We list the main ones here:
 \begin{enumerate}
@@ -1854,14 +1865,12 @@ end
 If you insert it in your \file{gdb.ini} file, you can look at a string with this
 function. There is a sample \file{gdb.ini} in appendix \ref{ch:GdbIniFile}.
 
-
 \item Objects are difficult to handle, mainly because \var{gdb} is oriented
 towards C and C++. The workaround implemented in \fpc is that object methods
 are represented as functions, with an extra parameter \var{this} (all
 lowercase !) The name of this function is a concatenation of the object type
 and the function name, separated by two underscore characters.
 
-
 For example, the method \var{TPoint.Draw} would be converted to
 \var{TPOINT\_\_DRAW}, and could be stopped at with
 \begin{verbatim}