Hi
Printed out a copy of the pascal-standards.text:
1. Table of Contents is at wrong end.
2. Suggest changing " aString: String " to " S: String "
You have 2 lines that are 100 cols in length. While most printing defaults to 80 cols for 8.5 inch paper you can set printer to elite which gives you 96 cols without line wrap. (I prefer 90 cols max so I can have an extra margin for 3 hole punch.)
Yes I know you can't always keep the line length to 96 or less and have the results look neat, but at least this change will help at times.
Russ
Russ Whitaker wrote:
Printed out a copy of the pascal-standards.text:
- Table of Contents is at wrong end.
That's a general problem of Texinfo in TeX mode (don't know really why, since LaTeX manages to put it at the right end).
Anyway, I wrote a script to reorder the DVI file. It's called dvi-reorder, and it's in p/script in GPC sources. It requires dviutils (dviselect and dviconcat).
- Suggest changing " aString: String " to " S: String "
Indeed. I copied these lines (as an example) from older code which does not conform to our rules about identifier names.
You have 2 lines that are 100 cols in length. While most printing defaults to 80 cols for 8.5 inch paper you can set printer to elite which gives you 96 cols without line wrap. (I prefer 90 cols max so I can have an extra margin for 3 hole punch.)
Yes I know you can't always keep the line length to 96 or less and have the results look neat, but at least this change will help at times.
Yes, line width is a difficult issue which is why we don't give fixed rules there. In this particular example, it's probably better to avoid the problem (just delete the last two lines, I think the other ones already make the point clear).
Frank
Hi Russ,
- Table of Contents is at wrong end.
I don't have clues how to tell `makeinfo' to put it where it belongs. I noticed now that there's the same problem in the HTML version, caused again by `makeinfo'. Any suggestion?
- Suggest changing " aString: String " to " S: String "
Not really. First of all, according the the GPCS (short for GNU Pascal Coding Standards) "S: String" should be "s: String". (Of course nobody can force anyone to apply the GPCS, they are just advice.) Secondly, "aString" is the result of a rule we haven't yet defined. It's the only one which hasn't been defined yet. If you grep for "FIXME" you'll find just one instance of it and you can read what it's about. I'll save you the grep which is hard for a printed copy. :-))
: In object oriented code (especially often in constructors), there is : often the need to have a parameter correspond to an object field : (e.g., to pass a value with which to initialize the field). Since : both can't be called the same, the field should have the ``natural'' : name since it's usually used in more routines, and the parameter : name should be ``mangled''. FIXME: We haven't found a really : satisfactory rule for mangling yet (some use ``a'' as a prefix), and : if you have any good idea, let us know.
You have 2 lines that are 100 cols in length.
I fixed those lines. I also tried to solve the problem for the lines of code by choosing another appropriate example from the GPC sources which doesn't need such long lines.
Thanks,
Nick
-
Frank Heckenbach -
Nicola Girardi -
Russ Whitaker