>-----Original Message----- >[mailto:[EMAIL PROTECTED] On Behalf Of Ben Wong > >I personally wouldn't use it for production websites because >it inflates the size of the Javascript file, therefore forcing >the user to download more. Also it would tempt others to steal >code by making it easy to understand. > >As a way of documenting code during development and for future >reference it would be useful, but well written code should be >self-documenting (well named functions) and easy to understand.
So does it make code easy to understand or not? Make your mind up!! Personally, I do try and make use of it, but there are some limitations which I am attempting to work around by writing a script to run at a higher level. Also, code bloat is not a problem, as I run all CSS, HTML and JS through a compaction process as I take it live (automated release system) For most small projects it probably doesn't give much advantage, but I don't really understand how any of the arguments against using JSdoc are different to using JavaDoc. Mike ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
