[Asterisk-Dev]About Asterisk Architecture

[Jerris, Michael MI]

Either file a bug for the patch, or if you are trolling, collect some
together and post them as a single documentation patch... Might as well
fix all the docs in a file at once :) 

> -----Original Message-----
> From: asterisk-dev-bounces at lists.digium.com 
> [mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of 
> Kristian Nielsen
> Sent: Monday, May 02, 2005 3:35 PM
> To: Asterisk Developers Mailing List
> Subject: Re: [Asterisk-Dev]About Asterisk Architecture
> 
> > > Ignore the comments in the code, a lot of them are just 
> plain wrong
> 
> > If they are wrong we need to get them out of there... can you point 
> > out an example?
> 
> >From include/asterisk/sched.h:
> 
>     /*!Adds a scheduled event */
>     /*! 
>      * \param con Schduler context to add
>      * \param when how many milliseconds to wait for event to occur
>      * \param callback function to call when the amount of 
> time expires
>      * \param data data to pass to the callback
>      * Schedule an event to take place at some point in the 
> future.  callback 
>      * will be called with data as the argument, when 
> milliseconds into the
>      * future (approximately)
>      * Returns 0 on success, -1 on failure
>      */
>     extern int ast_sched_add(struct sched_context *con, int 
> when, ast_sched_cb callback, void *data);
> 
> But it does not return 0 on success, it returns an id that 
> can be passed to ast_sched_del().
> 
> What's a good and quick way to get such trivias into the CVS, 
> file a new bug each time?
> 
>  - Kristian.
> 
> -- 
> Kristian Nielsen   kn at sifira.dk
> Development Manager, Sifira A/S
> 
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>