This is one of the things that caused me to pause. The core developers have enough to keep them busy without me bugging them to update Doxygen or git pull notes specifying things like this. But, I don’t have enough experience with C to decode what’s going on in the code a lot of times so I hit a wall. I’m pretty sure a script would just dump every variable declaration without context to inform of its use. I don’t know how to solve this problem. :-( Bote From: Freeswitch-docs [mailto:freeswitch-docs-bounces@lists.freeswitch.org] On Behalf Of Stanislav Sinyagin Sent: Friday, 16 February, 2018 13:56 To: FreeSWITCH Docs Team <freeswitch-docs@lists.freeswitch.org> Subject: Re: [Freeswitch-docs] Current Progress on Variables But many variables don't have #define statements and are used as literal strings in the code. On Feb 16, 2018 18:28, "Ryan Harris" <ryharris@airmail.cc <mailto:ryharris@airmail.cc> > wrote: Hi team, It's not all that useful yet, but I've attached a report that contains all variables the FreeSWITCH gets, accounting for constants that were #defined in the source. There are about 50 that my script wasn't able to interpret as variables. Either the script didn't pick up the constant or it was actual code and not a string. The report also does not account for variables that FreeSWITCH sets. I will work on those later. The catalog right now has 638 variables while the attached report has 774. _______________________________________________ Freeswitch-docs mailing list Freeswitch-docs@lists.freeswitch.org <mailto:Freeswitch-docs@lists.freeswitch.org> http://lists.freeswitch.org/mailman/listinfo/freeswitch-docs