Replace (removed) \FIXME command with comments
This commit is contained in:
parent
9a9d91fe92
commit
3163116a7d
|
@ -22,9 +22,9 @@ The server's response is always checked. If the server's response
|
|||
doesn't match the expected code from the server, a catchable
|
||||
\ex{ftp-error} is raised.
|
||||
|
||||
\FIXME{The source says you can look at pop3.scm to find out how to
|
||||
catch the ftp-error raised by some procedures this. We have not had
|
||||
a look there, yet.}
|
||||
%{The source says you can look at pop3.scm to find out how to
|
||||
%catch the ftp-error raised by some procedures this. We have not had
|
||||
%a look there, yet.}
|
||||
|
||||
\subsubsection*{Entry points }
|
||||
|
||||
|
|
|
@ -148,7 +148,7 @@ For those of you who are intrested, the table \ref{ftpd-commands}
|
|||
shows the list of supported commands by \ex{ftpd} according to
|
||||
RFC~959:
|
||||
|
||||
\FIXME{Can there be a pagebreak in a table?}
|
||||
%{Can there be a pagebreak in a table?}
|
||||
|
||||
|
||||
\begin{table}
|
||||
|
|
|
@ -23,9 +23,7 @@ the time by polling several independent sites on the network.
|
|||
Asks \semvar{host} about the current time. \semvar{tcp/udp} is
|
||||
either \ex{socket\=type/\ob{}stream} or
|
||||
\ex{socket\=type/\ob{}datagram}, that indicate TCP or UDP
|
||||
connection, respectively (depends on the server).\FIXME{Is it
|
||||
correct, that the tcp/udp argument describes TCP or UDP use via
|
||||
socket-type/stream or socket-type/datagram, resp.?} The number of
|
||||
connection, respectively (depends on the server). The number of
|
||||
second since 1970 is returned, since the time protocol returns the
|
||||
number of seconds since 1900, whereas Unix time is since 1970. The
|
||||
difference between both answers is 2208988800.
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
%
|
||||
|
||||
\section{Overview}
|
||||
\FIXME{Is toothless really R5RS, too?}
|
||||
%FIXME{Is toothless really R5RS, too?}
|
||||
These modules define an environment that is \RnRS without features that
|
||||
could examine or effect the file system. You can also use it as a
|
||||
model of how to execute code in other protected environments in \scm.
|
||||
|
|
|
@ -102,18 +102,11 @@ strings that are meant to be used in a URI.
|
|||
\end{defundesc}
|
||||
|
||||
\begin{defundesc}{resolve-uri} {cscheme cp scheme p} {scheme path}
|
||||
\FIXME{Sorry, I can't figure out what resolve-uri is inteded to do.
|
||||
Perhaps I find it out later.}
|
||||
|
||||
Nobody really knows what this procedure was intended to do.
|
||||
|
||||
The code seems to have a bug: In the body of receive, there's a
|
||||
loop. j should, according to the comment, count sequential \verb|/|.
|
||||
But \ex{j} counts nothing in the body. Either zero is added \ex{((lp
|
||||
(cdr cp-tail) (cons (car cp-tail) rhead) (+ j 0)))} or \ex{j} is
|
||||
set to 1 \ex{((lp (cdr cp-tail) (cons (car cp-tail) rhead) 1))}.
|
||||
Nevertheless, \ex{j} is expected to reach value \ex{numsl} that can
|
||||
be larger than one. So what? I am confused.
|
||||
%FIXME{Sorry, I can't figure out what resolve-uri is inteded to do.
|
||||
%Perhaps I find it out later.}
|
||||
%There is a paragraph in the spec, that describes someting like
|
||||
%resolve-uri does. We have to check this.
|
||||
To be done.
|
||||
\end{defundesc}
|
||||
|
||||
\begin{defundesc}{split-uri-path} {uri start end} {list}
|
||||
|
|
Loading…
Reference in New Issue