Paul Eggert wrote: > Your suggestion to use a followup > comment with fancy highlighting characters is less useful to my eyes; > I'm used to the more-standard convention of a short comment first.
So, what can we do? Moving the prologue's comment to another file would be bad. Comments should be very close to the code, otherwise they are overlooked. Would it help to reorder the file's header? Currently it has Prologue part 1 (2 lines with #!) Prologue part 2 Program short description Time stamp Copyright and license notice Written-by notice (needed for upholding copyright, at least in German courts [1]) Program long description Code How about if we reorder it to: Prologue part 1 (2 lines with #!) Copyright and license notice Written-by notice Program short description Program long description Prologue part 2 Time stamp Code Bruno [1] I'm referring to the Hellwig vs. VMware judgement.
