55 lines
1.6 KiB
TeX
55 lines
1.6 KiB
TeX
>%&latex -*- latex -*-
|
|
|
|
\chapter{Todo}
|
|
{\parindent 0pt
|
|
|
|
We'd love to have have people implement these subsystems and
|
|
fold them into the scsh release:
|
|
\begin{itemize}
|
|
\item More network protocols. Telnet and ftp would be the most important.
|
|
\item An ILU interface.
|
|
\item An RPC system, with ``tail-recursion.''
|
|
\item Interfaces to relational db's. This would be quite useful for
|
|
Web servers.
|
|
\end{itemize}
|
|
|
|
Manual hacking:
|
|
\begin{itemize}
|
|
\item The {\LaTeX} hackery needs yet another serious pass. Most importantly,
|
|
long procedure ``declarations'' need to be broken across two lines.
|
|
|
|
\item Fix up 0-or-more and 1-or-more parameter typesetting, with subscripts.
|
|
|
|
\item Parameter subscripts need to be made real subscripts.
|
|
|
|
\item Soup up the markup processor, and redo manual in markup. Generate
|
|
LaTeX, HTML, and info versions. Alternatively, persuade some kind
|
|
soul to hand-port manual to HTML or info.
|
|
\end{itemize}
|
|
|
|
Job control, after \ex{jcontrol.scm}
|
|
|
|
Static heaps; fast startup.
|
|
|
|
Gnu readline lib.
|
|
|
|
Interrupt system.
|
|
|
|
Make it all coexist with S48 threads as well as can be done for Unix.
|
|
The DEC SRC tech report gives a good discussion of the issues.
|
|
|
|
Testing broken symlinks---new value for \var{chase?} flag?
|
|
|
|
Rename and release \ex{ensure-file-name-is-\{non,\}directory}.
|
|
|
|
More informative errno exception packets \& documentation for them.
|
|
|
|
Other things should be available: hash tables, sort, list utils, pattern
|
|
matchers. But things start to overload. The module system is the appropriate
|
|
way to use these.
|
|
|
|
Need to do file-control (\ie, \ex{fcntl()}).
|
|
\ex{fcntl} is ugly.
|
|
Better to have a procedure for each different operation.
|
|
}
|