1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
"http://www.w3.org/TR/REC-html40/loose.dtd">
<HTML>
<!--
***********************************************************************
FUNNELWEB MANUAL WEB PAGE
=========================
Copyright (c) Ross N. Williams 1995-1999. All rights reserved.
Permission is granted to make and distribute verbatim copies of this
FunnelWeb manual provided that all notices (including, without
limitation, the copyright notice, this permission notice, any record
of modification, and all legal notices) are preserved on all copies.
Modified versions of this manual, including translations to other
languages, may be distributed under the same terms, provided that each
modification made to the manual since its original release by Ross N.
Williams (www.ross.net) is identified on the page on which it occurs,
and the front page of the manual carries a notice notifying the reader
that changes have been made, and referring the reader to the official
FunnelWeb website at www.ross.net/funnelweb/.
To the extent permitted by law there is ABSOLUTELY NO WARRANTY.
***********************************************************************
-->
<HEAD>
<TITLE>5.3 Suggestions From Users</TITLE>
<STYLE TYPE="text/css"> <!-- A {text-decoration: none} // --> </STYLE>
</HEAD>
<BODY BACKGROUND="binary/background.gif"
BGCOLOR="#FFFFFF"
TEXT="#000000"
VLINK="#660000"
LINK="#FF0000"
ALINK="#CC0000">
<TABLE WIDTH="590">
<TR>
<TD WIDTH="130" VALIGN="top">
<IMG SRC="binary/d_clear.gif" ALT="" WIDTH="130" HEIGHT="1"><BR>
<FONT SIZE="2">
<BR>
<A HREF="http://www.ross.net/"
TARGET="rosshome"
onClick="window.open('','rosshome','location,status,menubar,scrollbars,resizable',false).focus(); return true;"
>
<IMG SRC="binary/rossnet_logo.gif"
WIDTH="64" HEIGHT="32"
BORDER="0" ALT="RossNet"
HSPACE="0" VSPACE="1"></A><BR>
<BR>
<A HREF="../index.shtml"
TARGET="funnelweb"
onClick="window.open('','funnelweb','location,status,menubar,scrollbars,resizable',false).focus(); return true;"
>
<IMG SRC="binary/linklogo.gif"
WIDTH="64" HEIGHT="32"
BORDER="0" ALT="FunnelWeb"
HSPACE="0" VSPACE="1"></A><BR>
<BR>
<A HREF="../reference/index.html"
TARGET="funnelwebreference"
onClick="window.open('','funnelwebreference','location,status,menubar,scrollbars,resizable',false).focus(); return true;"
><FONT COLOR="#FFFFFF"><B>Reference</B></FONT></A><BR>
<BR>
<A HREF="../tutorial/index.html"
TARGET="funnelwebtutorial"
onClick="window.open('','funnelwebtutorial','location,status,menubar,scrollbars,resizable',false).focus(); return true;"
><FONT COLOR="#FFFFFF"><B>Tutorial</B></FONT></A><BR>
<BR>
<A HREF="index.html"><FONT COLOR="#FFFFFF"><B>Developer</B></FONT></A><BR>
<A HREF="compile.html"><FONT COLOR="#FFFFFF">1 Compile</FONT></A><BR>
<A HREF="design.html"><FONT COLOR="#FFFFFF">2 Design</FONT></A><BR>
<A HREF="implement.html"><FONT COLOR="#FFFFFF">3 Implement</FONT></A><BR>
<A HREF="modify.html"><FONT COLOR="#FFFFFF">4 Modify</FONT></A><BR>
<A HREF="misc.html"><FONT COLOR="#FFFFFF">5 Misc</FONT></A><BR>
<A HREF="gpl.html"><FONT COLOR="#FFFFFF">6 Licence</FONT></A><BR>
<BR>
<A HREF="search.html"><FONT COLOR="#FFFFFF"><B>SEARCH</B></FONT></A><BR>
</FONT>
</TD>
<TD WIDTH="460" VALIGN="top">
<FONT SIZE="3">
<A HREF="index.html"><IMG SRC="binary/title.gif"
WIDTH="316" HEIGHT="24"
BORDER="0" ALT="FunnelWeb Developer Manual"
HSPACE="0" VSPACE="0"></A>
<P><FONT SIZE="5">5.3 Suggestions From Users</FONT><BR>
<P>This page contains a list of features that FunnelWeb
users have suggested. The fact that a suggestion has been
made does not automatically mean that I agree with it or
that it will be implemented one day. However, most of the
suggestions are sound.
<P>The number in square brackets after each suggestion
indicates the number of users who have suggested the
feature.
<P>A quick look at this list suggests that future work on
FunnelWeb should be mainly directed towards improving its
typesetting facilities.
<P>
<PRE>
General
-------
S: Integrate FW into the Borland C++ development environment. [1]
S: Add a feature for updating FW source files after the product
files have been modified. [1]
Documentation
-------------
S: Improve the typesetting of the index. [1]
S: Add more entries to the index. [1]
S: Add a quick reference guide. [1]
Scanner
-------
S: Fix the bug that makes FunnelWeb bomb on excceptionally long input
lines. [1]
S: If a closing @} occurs at the start of a line, eliminate the
preceeding end of line. [1]
S: Allow TABS [1].
S: The syntax is ugly. Redesign it. [2]
Parser
------
S: Add named parameters for macros. [1]
S: Add conditionals. [1]
S: Add a feature that enables the user to specify that all the
macros called within a particular macros be defined in the order
in which they are called. [1]
Tangle
------
S: Allow line-oriented substitution and so on rather than stream
oriented. [1]
Weave
-----
S: Don't typeset non-leaf macros. This will avoid clutter. [1]
S: Teach FW C++ so it can typeset it nicely. [1]
S: Allow both FW text and TeX in the same document (two modes). [1]
S: Include greater support for typesetting a program as a book. [1]
"What we need is a facility for TANGLING small WEB files
into small source files, but WEAVING those same small
WEB files into a single large documentation file, without
the seams becoming apparent."
S: Add a new format: Microsoft Rich Text Format (RTF). [2]
S: Write a program to convert an RTF file into FunnelWeb source.
Then people can edit programs in MSWord and run them through
FunnelWeb. [1]
S: Detailed notes on indexing from one user: [1]
S: Add the ability to include typeset comments within program text. [2]
R: The @[..@] syntax has been reserved for this.
S: Add a new format: LaTeX. [1]
S: Add a new format: Plain ASCII text. [1]
S: Add a GENERIC language typesetting facility: [1]
"Have you seen the program 'vgrind' (for TeX) or 'psgrind' (for
PostScript)? It contains a termcap-like database of programming
language features, e.g. format of a label, format of a
producedure/function, keyword listings, character string quoting
rules, etc. Perhaps this would be useful for FW?"
S: Automatically generate an index. [1]
S: Allow @" and @" in documentation to typeset double quotes properly. [1]
S: Detailed comments from one correspondent:
"The ability to generate a cross reference of identifiers
(variables and functions) is essential.
Constants are generally defined only in 1 place
and so a cross reference to the definition
macro is useful.
Variables are generally declared in 1 place but
refered to and defined in multiple places.
A cross reference to the declaration site
is generally not useful.
A cross reference to the site of use is
confusing, since there may be many, equally
important sites where the variable is assigned
a value.
functions are generally unique and so a cross reference
to the site of definition (or declaration in
the absense of a definition) is useful.
In FWEB (which I have used extensively recently) each instance
of use of an identifier contains a subscript which points
to the site of definition of the identifier (I think this
is what you refer to in the documents as a feature of the
original WEB.) The fact that locating identifiers requires
knowledge of the programming language is true."
Documentation
-------------
Page 34, section 1.7.2, paragraph 2, last sentence:
"free text be default" should be "free text by default".
Page 34, section 1.7.3, paragraph 1, 1st sentence:
"divide and conquor" should be "divide and conquer"
Page 35, section 1.73, paragraph 2 on page 35:
"section heading at level n cannot....at level (n-1) or less."
I think this should be:
"section heading at level n cannot.. at less than level (n-1)"
Otherwise you are saying that level C cannot occur at B or less.
Page 50, section 2.11, last paragraph, line 10 of para:
"excessibly" should be "excessively"
In the example on p. 21, "... the string ``Hello World''" looks like a TeX
dependent hangover.
The caption under Fig. 4, p.111 came out badly spaced on our system.
Isn't it `holistic' rather than `wholistic?'
There is often a need to have version dependent documentation as well
as version dependent code. It would be nice if there was a special
kind of macro that could run the output to a file through the
typesetter, i.e., generate TeX files. Meanwhile, you can get some
interesting effects by letting FunnelWeb generate .fw files! You
might like to mention this exciting possibility in V2 of the user
manual.
</PRE>
<P>
<TABLE WIDTH="100%">
<TR>
<TD ALIGN="left" VALIGN="bottom"><A HREF="misc_wishlist.html"><IMG SRC="binary/fw_left.gif" HEIGHT="32" WIDTH="32" BORDER="0" ALT="Prev"></A></TD>
<TD ALIGN="center" VALIGN="bottom"><A HREF="misc.html"><IMG SRC="binary/fw_up.gif" HEIGHT="32" WIDTH="32" BORDER="0" ALT="Up"></A></TD>
<TD ALIGN="right" VALIGN="bottom"><A HREF="misc_knownbugs.html"><IMG SRC="binary/fw_right.gif" HEIGHT="32" WIDTH="32" BORDER="0" ALT="Next"></A></TD>
</TR>
</TABLE>
<P>
<HR>
<FONT SIZE="2">
<A HREF="mailto:webmaster@ross.net">Webmaster</A>
<A HREF="copyright.html">Copyright © Ross N. Williams 1992,1999. All rights reserved.</A><BR>
</FONT>
</FONT>
</TD>
</TR>
</TABLE>
</BODY>
<!-- *********************************************************************** -->
<!-- End Of A FunnelWeb Manual Web Page (www.ross.net/funnelweb/) -->
<!-- *********************************************************************** -->
</HTML>
|
