Re: [Doxygen-users] Adding Custom Commands to execute Shell Scripts

[Rosen D. <ros...@gm...>]

Hi all,

I wasn't sure what message to take from the last email responses.

Does everyone agree that a \shell command would be awesome, and we
just don't have someone to add this feature.

Or is everyone on the side of doing some magic with INPUT_FILTER and a
\shell command is really a bad idea?

thanks,
rosen,

2010/7/18 Rosen Diankov <ros...@gm...>:
> There are two things:
>
> - have to make sure we are in a c++ comment, this is tricky due to strings
> and the  preprocessor. Accidentally replacing code could affect the
> structure of the classes.
>
> - we paste code in the comments in verbatim blocks in doxygen. I do not want
> anything being accidentally repalced there.
>
> Rosen,
>
> On Jul 18, 2010 9:40 AM, "Eric J. Holtman" <er...@ho...> wrote:
>
> On 7/18/2010 7:42 AM, Rosen Diankov wrote:
>>
>> Because i want things done correctly, the INPUT_FILTE...
>
> I think you're not understanding something.  Why do you
> need to parse any syntax at all?
>
> If the commands look like $OUTPUT_GOES_HERE ('cat /etc/passwd')
>
> can't you just write a simple filter that looks for the token
> $OUTPUT_GOES_HERE
> then gathers everything between the parens, execs your command,
> captures the output, and replaces it?
>
> What doxygen (or c++) syntax do you need to parse?
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>