You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, autogsdoc tries to be smart and puts as dates those found in the header (.h first, .m if not present). It scavenges for Date, Copyright and if present Revision too. However the latter one is CVS info, not really useful.
These dates are referred to the file content.
I think somewhere (maybe at the bottom or top of the file in a different style) a generation file of the doc itself should be present. This informs the user on when the generation was run, independently of when the class was last touched itself (and maybe somebody forgot to update its header copyrights).
Yes, this stuff seems obsolete (and perhaps never very useful to start with).
I agree that having a documentation generation timestamp (the date/time at which the headers/source were parsed) might be nice.
Currently, autogsdoc tries to be smart and puts as dates those found in the header (.h first, .m if not present). It scavenges for Date, Copyright and if present Revision too. However the latter one is CVS info, not really useful.
These dates are referred to the file content.
I think somewhere (maybe at the bottom or top of the file in a different style) a generation file of the doc itself should be present. This informs the user on when the generation was run, independently of when the class was last touched itself (and maybe somebody forgot to update its header copyrights).
What do you think? @rfm @gcasa
The text was updated successfully, but these errors were encountered: