Re: [Groff] Creating a table macro

[Automation Department]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I agree, "tricks" can adversely affect code sustainability.
Documentation/comments, as you touch on, does mitigate this somewhat.

Thanks for the advice!

Chad Roseburg
Automation Dept.
North Central Regional Library
509-663-1117  x.134
800-426-READ  x.134
509-630-5413  cell

On 05/19/2011 04:07 PM, Clarke Echols wrote:
> 
> 
> Tadziu Hoffmann wrote:
>>> I see now, that for most purposes, macros involving
>>> preprocessors should be avoided.
>>
>> For the most part, yes.  There probably *are* some cool tricks
>> you can do, but they would require a good idea of what happens
>> internally.
> 
> One caution:
> 
> There may be some "neat tricks" you can use, but be careful to
> make sure you comment your code *thoroughly* -- especially if
> you're in a situation where someone else may come along who has
> to pick up your responsibilities if or when you're gone or move
> on to other things.
> 
> Having lots of comments -- especially inside of macro files, etc.
> -- has saved me many hours years later when I try to figure out
> what I was doing way back when.
> 
> And your successors will appreciate it.
> 
> That's good advice anywhere, groff, XHTML, CSS, -- anywhere.
> 
> Clarke
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJN1becAAoJEBi1nVMf5Zz5/AUIAK0Q6qRexP1rvKKlEuyayKfB
Dy9aWpWiaI4jjF/c3aDBCyon+E3Uq/vAiv7kWZ/8dPMKlY2cHrcqJuT5akqrUSwp
/95MIJ8BLk6n7K2AXG5k8cRvb6yU/H4wnmAto7bX6QCWQUAPhJnemGMLm0iuNRB0
bk1OPmdxLicxlDYAgjk//1I3T0fALJALns+DlBEXwJlEBg0zGy4+L7EXQ7itj+Bc
GXsECMecZ+3iA75aUVNXwd/LHGLhWf1E8QwWfIKnbE+g1o3H/nFcVueeGHt3LRjG
DvND32Hj+fFM/Yx1IDrB8Huy708bN7nM2gDrbwp9tB5VHuGTK05tnAcw7vk5eOE=
=kubh
-----END PGP SIGNATURE-----