On Mon, Sep 27, 2010 at 03:16:09PM -0500, Gabriel M. Beddingfield wrote: > > > On Mon, 27 Sep 2010, Arnold Krille wrote: > > >And I was talking about "help(someclass.function)" inside python to get the > >documentation for that python class. Try that in C(++) :-) > > Thank you!! I had no idea that existed. This beats the heck out of > doing `print someclass.function.__doc__` all the time. guys ? use a proper python shell. ipython is there for quite some time. and i recently discovered bpython http://ipython.scipy.org/moin/ http://bpython-interpreter.org/ this is where the fun starts also help() works nicely on instances. doctests also pretty much kick ass. http://docs.python.org/library/doctest.html one of the problems with python and big projects is in my opinion that it dynamically typed. and refactoring stuff in python can get pretty awkward. type errors are only detected at runtime. so you need to have your test coverage in the 80% realm. nose-tests helps you a bit with this stuff. including coverage analysis, etc. http://somethingaboutorange.com/mrl/projects/nose/0.11.2/index.html > > As for C/C++... the libc and libstdc++ man pages are about the same. > Plus, `apropos` kicks butt. > > -gabriel > _______________________________________________ > Linux-audio-user mailing list > Linux-audio-user@xxxxxxxxxxxxxxxxxxxx > http://lists.linuxaudio.org/listinfo/linux-audio-user -- torben Hohn _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
