That would assume that the underlying code is perfect, which it probably isn't. Not knocking the efforts, but in my view, you can't have too much in line documentation. I hope to make a contribution shortly. Right now I'm updating the WIKI where appropriate. Top level examples should work with a cut and paste, if they don't you're going to alienate new entrants.
Regards -----Original Message----- From: freeswitch-users-boun...@lists.freeswitch.org [mailto:freeswitch-users-boun...@lists.freeswitch.org] On Behalf Of Jason White Sent: 13 February 2009 23:24 To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] FS 1.0.2 Crash and burn Nik Middleton <nik.middle...@noblesolutions.co.uk> wrote: > Code > I've looked at so far is very neat, but boy is there a lack of in-line > comments. Haven't looked at the main source yet though. I always used > to work on 3 lines of comments to 1 major line of code. Call me > pedantic, but it aids maintenance. I find the FreeSWITCH code quite readable. Public API functions have comments, which are all that we need, I think. _______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org _______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
