lynx-dev programming documentation

[Philip Webb]

990208 Kim DeVaughn wrote: 
> I dunno the best place to document that "limitation" overall though ..
> .. perhaps in the README and/or ABOUT-NLS file(s).
> Or maybe there should be some kind of INTERNALS file,
> for documenting such things, which would also include things
> about var/fn() naming conventions, macro usage (eg, FREE() vs. free()),
> "style, coding conventions, and the like.
 
exactly!  another long-felt want!
more people would dip their toe in Lynx source code,
if they didn't have to start learning everything from scratch.
i'm thinking of people like me, who can write simple C programs,
but have no idea what counts as an industry-wide convention,
a Lynx idiosyncracy or a bit of patchwork from the back of someone's envelope.
one large area of confusion is the WWW material called by Lynx,
which is all stored in another subdirectory.

-- 
========================,,============================================
SUPPORT     ___________//___,  Philip Webb : address@hidden
ELECTRIC   /] [] [] [] [] []|  Centre for Urban & Community Studies
TRANSIT    `-O----------O---'  University of Toronto