On Sat, 25 Feb 2012, Frank Church wrote:
How about the reluctance to put documentation in library code? The policy with fpdoc is to create documentation separately from code. The problem is who has time for that. If documentation goes into the code it is better as it forces you to think clearly about what your are doing as you are doing that knowing that others depend on it, especially if there is a strict community code of ensuring that docs in the code are always correct and up to date, and that if they are not accurate they should be removed altogether. I am developing a FreePascal Lazarus program now, owing to my familiarity with Delphi, but at the same time I am keenly aware that in domains I am unfamiliar with I would probably better using Java, Python because the tools and libraries would be much better.
You don't need to choose. FPC can produce Java Bytecode and can leverage the whole Java API and all Java libraries. I just wrote an article on how to write an Android app, using only the Android Java APIs. It's remarkably easy. Michael. -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
