Hi
Merry Xmas
If you like to keep paper copies of your source files and would like to print on both sides of the paper you might like the attached source file. Also, it adds a margin for 3-hole punch.
enjoy, Russ
Russ Whitaker wrote:
Merry Xmas
If you like to keep paper copies of your source files and would like to print on both sides of the paper you might like the attached source file. Also, it adds a margin for 3-hole punch.
Thanks for the contribution. I didn't test it since I have only access to PostScript printers at university. Just a little comment on the code, though:
{$define ESC char(27)}
Is there any problem with using a constant (ESC = char (27))? Macros are a GPC extension (and quite ugly IMHO ;-), and a constant seems to work fine AFAICT.
Also, I'd suggest to use chr (a proper Pascal function) rather than char (a type-cast), also in other places, and to use '' rather than "" for normal text strings ("" is also a GPC extension, probably not known by many other compilers -- the difference is that "" allows C-style escapes, so you'll need it for TABS etc., but not for most other strings).
Frank
Hi
On Fri, 29 Dec 2000, Frank Heckenbach wrote:
Russ Whitaker wrote:
If you like to keep paper copies of your source files and would like to print on both sides of the paper you might like the attached source file. Also, it adds a margin for 3-hole punch.
Thanks for the contribution. I didn't test it since I have only access to PostScript printers at university. Just a little comment on the code, though:
{$define ESC char(27)}
Is there any problem with using a constant (ESC = char (27))? Macros are a GPC extension (and quite ugly IMHO ;-), and a constant seems to work fine AFAICT.
Admittedly this wasn't a good use for $define. Was trying it out and just left it in. (A better use might be {$define asm asmname} because some of the source lines in the units are rather long and I don't have a wide carrage printer.)
Also, I'd suggest to use chr (a proper Pascal function) rather than char (a type-cast), also in other places, and to use '' rather than "" for normal text strings ("" is also a GPC extension, probably not known by many other compilers -- the difference is that "" allows C-style escapes, so you'll need it for TABS etc., but not for most other strings).
OK
Aso, please make minor correction: In section "check for existing TOF" add a "continue" statement thus:
[..] NewPage; continue; end;
Historical footnote: wrote original in A86 assembly 15 years ago.
Thanks Russ
Russ Whitaker wrote:
{$define ESC char(27)}
Is there any problem with using a constant (ESC = char (27))? Macros are a GPC extension (and quite ugly IMHO ;-), and a constant seems to work fine AFAICT.
Admittedly this wasn't a good use for $define. Was trying it out and just left it in. (A better use might be {$define asm asmname} because some of the source lines in the units are rather long and I don't have a wide carrage printer.)
If you mean the units written by me, this won't help much as some lines are much longer. ;-)
What could be done is to split the lines automatically, like the pas2texi script (included in GPC source distributions, but written in sed not Pascal) does to include the unit interfaces in the manual.
Aso, please make minor correction:
If you expect that I'm somehow maintaining or keeping the official version, I don't intend to do it actually...
Peter and I have discussed creating a place on agnes for such contributions, together with short descriptions (somewhat similar to LSM) and an index, created automatically from them...
In section "check for existing TOF" add a "continue" statement thus:
[..] NewPage; continue;
end;
Historical footnote: wrote original in A86 assembly 15 years ago.
Congratulations, the code doesn't look like it (-: no gotos including break or continue, except the one above)...
Frank