Commit 0188dd31 authored by kollo's avatar kollo

New release of the manual, now use pstotext to make ...

... X11-Basic-manual-1.25.txt (Issue by Roger Greenlaw - 2017-02-28)
little (minor) add in making list of error messages for the manual
parent ced2fee8
......@@ -78,11 +78,13 @@ $(NAME)-$(VERSION).txt : sec-base/*.sec sec/*.sec 39_Errors.sec main.otxt ../FAQ
echo " Last change to this file: " `date` >> $@
chmod 644 $@
mv $@ Outputs/
39_Errors.sec: bas/do_the_error_section.bas
39_Errors.sec: bas/do_the_error_section.bas ../../src/errortxt.c
rm -f $@; xbasic bas/do_the_error_section.bas > $@
main.otxt : main.dvi
dvi2tty -w132 main.dvi -o $@
#main.otxt : main.dvi
# dvi2tty -w132 main.dvi -o $@
main.otxt : main.ps
pstotext -cork -output $@ $<
main.dvi : A.tex tex/*.tex $(EPSFILES) 39_Errors.sec
latex tex/main.tex
makeindex main.idx
......
......@@ -208,10 +208,11 @@ DESCRIPTION:
is given, the fill will stop at any other color than the one of
the starting coordinate.
The fill color can be chosen with the command COLOR.
COMMENT:
The FILL command does not work when the linewidth is set to anything
other than 1 pixel. Please use DEFLINE to set the linewidth back to 1
before using FFILL in that case.
before using FILL in that case.
SEE ALSO: COLOR, DEFLINE
#############################################################################
......
......@@ -140,13 +140,18 @@ functions may not work, especially pointer aritmetric (\verb|VARPTR()|,
will probably lead to segmentation faults when using huge amounts of
memory.\footnote{In X11-Basic all pointers to memory adresses are stored in
32bit integer variables. The upper 32bits of the adresses are stored internally
fur further use. So if you calculate VARPTR(a), you would be able to
for further use. So if you calculate VARPTR(a), you would be able to
POKE to the adress immediately after without error, because the upper part of
the adresses was stored intenally from the previous call to VARPTR.
X11-Basic will emmit a warning,
pointer base has changed, whenever this part is different from what it
was before. This way, pointer aritmetrics can be used with care, even on 64 bit
operating systems.}
operating systems.} It has turned out, that also the GEM AES graphics functions
make use of pointer conversions (to stay compatible with the anchent ATARI ST format),
also here a problem might occur. Also the staticlly linked versions of X11-Basic are
more likely to work correctly, because the shared libraries are loaded to the upper
address space. So If you see the WARNING messages, try to use a static version of
X11-basic (\verb|xbasic.static|).
\subsection*{Compiling X11-Basic from its sources under UNIX like systems}
\index{Compiling}
......@@ -172,7 +177,8 @@ the functionality of X11-Basic.).
\begin{enumerate}
\item Install the development environment packages, e.g. done by the command:
\begin{verbatim}
sudo apt-get install libx11-dev libreadline6-dev liblapack-dev libgmp-dev
sudo apt-get install libx11-dev libreadline6-dev liblapack-dev \
libgmp-dev libfftw-dev
\end{verbatim}
\item Unpack \verb|X11Basic-1.25.tar.gz| with
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment