doxygen-users — List for users of doxygen

Re: [Doxygen-users] Doxygen .txt file inclusion

[Albert <alb...@gm...>]

Hi Thomas,

It is not 100% clear what you want to achieve, but have you looked at
EXTENSION_MAPPING and at the markdown possibilities?

Albert


On Mon, Jan 6, 2014 at 2:56 PM, Thomas Nemeth <nem...@gm...>wrote:

>
>     Hi.
>
>     I'd like to include in my projects documentation, some doxygen
> documentation
>     that lies in a non-source-code file (eg: .txt). Up to new I had to
> manually
>     copy/paste (well, not really manually, but using head/cat/tail using a
> makefile)
>     into a .h file so that the titlepage and some general documentation is
> included.
>
>     However, this is a bit non portable. I've searched through the
> documentation to
>     know if a special command could include such a file. But all I could
> find is
>     \include which is like including code. But I'd like to include
> documentation
>     with \section, \subsection and all...
>
>     Is there anything like that ?
>
>
> Thomas.
>
> --
> | A: Yes.
> | >Q: Are you sure?
> | >>A: Because it reverses the logical flow of conversation.
> | >>>Q: Why is top posting frowned upon?
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
> Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>
>

[Doxygen-users] Doxygen .txt file inclusion

[Thomas N. <nem...@gm...>]

    Hi.

    I'd like to include in my projects documentation, some doxygen
documentation
    that lies in a non-source-code file (eg: .txt). Up to new I had to
manually
    copy/paste (well, not really manually, but using head/cat/tail using a
makefile)
    into a .h file so that the titlepage and some general documentation is
included.

    However, this is a bit non portable. I've searched through the
documentation to
    know if a special command could include such a file. But all I could
find is
    \include which is like including code. But I'd like to include
documentation
    with \section, \subsection and all...

    Is there anything like that ?


Thomas.

-- 
| A: Yes.
| >Q: Are you sure?
| >>A: Because it reverses the logical flow of conversation.
| >>>Q: Why is top posting frowned upon?

Re: [Doxygen-users] non-collapsible section in CHM

[Albert <alb...@gm...>]

On my windows 7 machine I can collapse and expand the "Special Commands"
section without problems.
As far as I can see it looks like a local problem (which version of Windows
are you using?) or maybe it is a special sequence of steps, can you
reproduce the problem and describe the steps you made getting into this
state?



On Fri, Jan 3, 2014 at 10:38 PM, Ron Wilson <ron...@gm...> wrote:

> Don't know if this is a Doxygen bug or Microsoft help viewer bug, but in
> the Doxygen compressed help, the "Special Commands" section expanded, but I
> can't collapse it.
>
> Screen picture attached.
>
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
> Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>
>

Re: [Doxygen-users] epstopdf: command not found ON MAC MAVERICKS

[Michael P. <mpo...@co...>]

Hello Dimitri,
	I'm sorry to have taken so long to give this a shot.
	I did run the terminal instruction (substituting the folder I thought was the proper one) and did get some information when I asked it for its version.
	However, DOxygen still gives me the error messages.

Regards,
Mike

Michael Powell
P. O. Box 567
Boulder Creek, CA 95006
(408) 529-0864 (mobile)
mpo...@co...
http://home.comcast.net/~mpowell-programming
http://www.linkedin.com/in/michaelhpowell




On Dec 21, 2013, at 7:51 AM, Dimitri van Heesch <do...@gm...> wrote:

> Hi Michael,
> 
> On 20 Dec 2013, at 0:43 , Michael Powell <mpo...@co...> wrote:
> 
>> Hello,
>> 	I am using DOxygen to document an iPhone application. The context is Mac OS 10.9.1 with DOxygen 1.8.5. I got the TEX package from MacTEX. It's in a TEX subfolder to Applications and the release level on LaTeXiT is 2.5.4.
>> 	When I use the DOxygen Wizard to "Run doxygen", I get the following error message with (cursory impression) every class:
>> "sh: epstopdf: command not found
>> error: Problems running epstopdf. Check your TeX installation!"
>> 	This topic is not a new one, but I can't see from a Google search how to make it stop.
>> 	If one looks, there is some mention of epstopdf down there (/usr/local/texlive/2013/texmf-dist/scripts/epstopdf/epstopdf.pl), but I'm enough of a Neanderthal that I can't judge whether that's enough, or how DOxygen should know how to find it (if it doesn't already know).
> 
> I'm not 100% sure this is the same epstopdf (mine came with macports and is located here /opt/local/libexec/texlive/binaries/epstopdf).
> You could make a symlink to it by running the following in a terminal:
> 
> sudo ln -s /usr/local/texlive/2013/texmf-dist/scripts/epstopdf/epstopdf.pl /usr/local/bin/epstopdf
> 
> Then running 'epstopdf --version' in the terminal should print some version info.
> Once that works, doxygen will probably also be able to find it.
> 
> Regards,
>  Dimitri
> 

Re: [Doxygen-users] LaTeX environment cases: no line break

[Jannick <jan...@gm...>]

Stefan Pendl <stefan.pendl.71 <at> gmail.com> writes:

> 
> Am 23.12.2013 12:49, schrieb Jannick:
> > I think this package is one of the basic ones for LaTeX documents with
> > formulae.
> Jannick,
> 
> ... and that is the point, if you don't use formulas, you don't need it.
> 
> In my case there is no use for formulas in documentation, so why should 
> I include it?
> 
>  From a developers point of view, I only include those things that are 
> really always needed out of the box, for anything else I offer the 
> ability to include it on demand.

Stefan,

to make it very clear (again - since you seem to have cut off the relevant
part from my posting): I can live pretty well with putting the additional
LaTeX package into the config slot. I believe there are better issues to
discuss than what is required by every user and what is not (Cf., e.g., the
posting a minute ago I have put on top of the archive again - here any help
or enlightening hints will be highly appreciated).

Thanks anyways.

Cheers and Merry Xmas to everyone,
J.

Re: [Doxygen-users] Include external latex documentation

[Jannick <jan...@gm...>]

Jannick <jannick.news <at> gmail.com> writes:

> 
> Hi,
> 
> I suspect this is an evergreen issue, but I could find anything in the
> archive so far:
> 
> How can I add external latex documents into the doxygen documentation? I
> think this should be appear as some include statement in refman.tex.
> Unfortunately I could not figure out what the statement in the code
> documentation should be calling for tex files. I intend to write tex files
> for different routines which should be imported right to the code
> documentation of the routine itself.
> 
> FUP: Are there any problems in the combined latex output with internal and
> mutual references between the external latex file and the doxygen latex files?
> 
> Help and comments highly appreciated!
> 
> Best
> J.

Hi,

the below to bring this up again. Are there any easy ways to include
external LaTeX documentation

1 - into the html/.chm documentation
2 - into the LaTeX documentation

without any different treatment between (1) and (2) above? (2) could be
captured by \latexonly \include{../doc.tex} \endlatexonly which excludes
this piece of documentation from the html version.

Any help on this will be highly appreciated.

Cheers & Merry Xmas,
J.

Re: [Doxygen-users] LaTeX environment cases: no line break

[Stefan P. <ste...@gm...>]

Am 23.12.2013 12:49, schrieb Jannick:
> I think this package is one of the basic ones for LaTeX documents with
> formulae.
Jannick,

... and that is the point, if you don't use formulas, you don't need it.

In my case there is no use for formulas in documentation, so why should 
I include it?

 From a developers point of view, I only include those things that are 
really always needed out of the box, for anything else I offer the 
ability to include it on demand.


--
Stefan P.

Top-posting:
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Re: [Doxygen-users] LaTeX environment cases: no line break

[Jannick <jan...@gm...>]

Dimitri van Heesch <doxygen <at> gmail.com> writes:

> > Thx for your quick reply. Meanwhile solved: LaTeX package amsmath required
> > which could be added as the list of standard packages I believe.
> 
> Why should that be done if it is only used by your particular formula? 
> Note that you can use EXTRA_PACKAGES to specify additional LaTeX packages.

The EXTRA_PACKAGES feature already used, however many thanks for pointing it
out here for the benefit of other users. 

Re use of the amsmath package: Where do you know that the quoted
documentation lines are in the whole universe the only and single ones using
this feature? ;) 

I think this package is one of the basic ones for LaTeX documents with
formulae. But I can surely live with putting it into the EXTRA_PACKAGES slot.


Many thanks again and Merry Xmas,
J.

Re: [Doxygen-users] Segfault when using tag files from documentation that has been compiled using tag files

[JohnOldman <j.r...@wa...>]

Dimitri van Heesch-2 wrote
> On 22 Dec 2013, at 12:31 , JohnOldman <

> j.r.greis@.ac

> > wrote:
> 
>> UPDATE:
>> I've tried now with a whole bunch of different versions and it seems like
>> the problem first arises as of 1.6.2:
>> 1.6.1 and 1.6.0 work, 1.6.2 and about half a dozen other newer versions
>> I've
>> tried give me the same segfault. Could this be an incompatibility with my
>> distribution? I'm using Scientific Linux 6.
> 
> It is more likely a bug in doxygen introduced in 1.6.2 and triggered by
> your specific example.
> Can you grab the latest doxygen source from GitHub and compile it using
> ./configure --debug and then run it from a debugger and/or from valgrind. 
> That might give an indication where the problem is located.
> 
> Regards,
>   Dimitri

Hi Dimitri,
Thank you for your quick reply. I ran it with valgrind, here is the valgrind
output before and after the output from doxygen:

==25031== Memcheck, a memory error detector
==25031== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==25031== Using Valgrind-3.9.0 and LibVEX; rerun with -h for copyright info
==25031== Command: ./test.sh
==25031== 
==25032== 
==25032== HEAP SUMMARY:
==25032==     in use at exit: 44,907 bytes in 1,004 blocks
==25032==   total heap usage: 1,843 allocs, 839 frees, 117,565 bytes
allocated
==25032== 
==25032== 493 bytes in 1 blocks are definitely lost in loss record 285 of
302
==25032==    at 0x4A06AAA: malloc (vg_replace_malloc.c:291)
==25032==    by 0x465E62: xmalloc (in /bin/bash)
==25032==    by 0x42F7ED: execute_command_internal (in /bin/bash)
==25032==    by 0x432CED: ??? (in /bin/bash)
==25032==    by 0x433109: ??? (in /bin/bash)
==25032==    by 0x42FE9C: execute_command_internal (in /bin/bash)
==25032==    by 0x430BED: execute_command (in /bin/bash)
==25032==    by 0x41D535: reader_loop (in /bin/bash)
==25032==    by 0x41CCF8: main (in /bin/bash)
==25032== 
==25032== LEAK SUMMARY:
==25032==    definitely lost: 493 bytes in 1 blocks
==25032==    indirectly lost: 0 bytes in 0 blocks
==25032==      possibly lost: 0 bytes in 0 blocks
==25032==    still reachable: 44,414 bytes in 1,003 blocks
==25032==         suppressed: 0 bytes in 0 blocks
==25032== Reachable blocks (those to which a pointer was found) are not
shown.
==25032== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==25032== 
==25032== For counts of detected and suppressed errors, rerun with: -v
==25032== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 4 from 4)


==25031== 
==25031== HEAP SUMMARY:
==25031==     in use at exit: 42,199 bytes in 917 blocks
==25031==   total heap usage: 1,155 allocs, 238 frees, 63,414 bytes
allocated
==25031== 
==25031== LEAK SUMMARY:
==25031==    definitely lost: 0 bytes in 0 blocks
==25031==    indirectly lost: 0 bytes in 0 blocks
==25031==      possibly lost: 0 bytes in 0 blocks
==25031==    still reachable: 42,199 bytes in 917 blocks
==25031==         suppressed: 0 bytes in 0 blocks
==25031== Reachable blocks (those to which a pointer was found) are not
shown.
==25031== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==25031== 
==25031== For counts of detected and suppressed errors, rerun with: -v
==25031== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 4)

I hope this is what you meant, I am still relatively new to Linux...



--
View this message in context: http://doxygen.10944.n7.nabble.com/Segfault-when-using-tag-files-from-documentation-that-has-been-compiled-using-tag-files-tp6414p6423.html
Sent from the Doxygen - Users mailing list archive at Nabble.com.

Re: [Doxygen-users] LaTeX environment cases: no line break

[Dimitri v. H. <do...@gm...>]

On 22 Dec 2013, at 12:18 , Jannick <jan...@gm...> wrote:

> Dimitri van Heesch <doxygen <at> gmail.com> writes:
> 
>>> \f[
>>> x=\begin{cases}
>>> a & \varepsilon=0\\
>>> b & \varepsilon=1\\
>>> c & \varepsilon=2
>>> \end{cases}
>>> \f]
>>> 
>>> Happy to file a bug if needed. Just give me a shout.
>> 
>> Yes, please do, and please attach a self-contained example (source+config
> file in zip or tar) to the bug
>> report 
>> so it easy for me to reproduce.
> 
> Thx for your quick reply. Meanwhile solved: LaTeX package amsmath required
> which could be added as the list of standard packages I believe.

Why should that be done if it is only used by your particular formula? 
Note that you can use EXTRA_PACKAGES to specify additional LaTeX packages.

Regards,
  Dimitri

Re: [Doxygen-users] Segfault when using tag files from documentation that has been compiled using tag files

[Dimitri v. H. <do...@gm...>]

On 22 Dec 2013, at 12:31 , JohnOldman <j.r...@wa...> wrote:

> UPDATE:
> I've tried now with a whole bunch of different versions and it seems like
> the problem first arises as of 1.6.2:
> 1.6.1 and 1.6.0 work, 1.6.2 and about half a dozen other newer versions I've
> tried give me the same segfault. Could this be an incompatibility with my
> distribution? I'm using Scientific Linux 6.

It is more likely a bug in doxygen introduced in 1.6.2 and triggered by your specific example.
Can you grab the latest doxygen source from GitHub and compile it using ./configure --debug and then run it from a debugger and/or from valgrind. 
That might give an indication where the problem is located.

Regards,
  Dimitri

Re: [Doxygen-users] Segfault when using tag files from documentation that has been compiled using tag files

[JohnOldman <j.r...@wa...>]

UPDATE:
I've tried now with a whole bunch of different versions and it seems like
the problem first arises as of 1.6.2:
1.6.1 and 1.6.0 work, 1.6.2 and about half a dozen other newer versions I've
tried give me the same segfault. Could this be an incompatibility with my
distribution? I'm using Scientific Linux 6.



--
View this message in context: http://doxygen.10944.n7.nabble.com/Segfault-when-using-tag-files-from-documentation-that-has-been-compiled-using-tag-files-tp6414p6420.html
Sent from the Doxygen - Users mailing list archive at Nabble.com.

Re: [Doxygen-users] LaTeX environment cases: no line break

[Jannick <jan...@gm...>]

Dimitri van Heesch <doxygen <at> gmail.com> writes:

> > \f[
> > x=\begin{cases}
> > a & \varepsilon=0\\
> > b & \varepsilon=1\\
> > c & \varepsilon=2
> > \end{cases}
> > \f]
> > 
> > Happy to file a bug if needed. Just give me a shout.
> 
> Yes, please do, and please attach a self-contained example (source+config
file in zip or tar) to the bug
> report 
> so it easy for me to reproduce.

Thx for your quick reply. Meanwhile solved: LaTeX package amsmath required
which could be added as the list of standard packages I believe.

Cheers,
J.

Re: [Doxygen-users] LaTeX environment cases: no line break

[Dimitri v. H. <do...@gm...>]

On 21 Dec 2013, at 14:34 , Jannick <jan...@gm...> wrote:

> It appears the the LaTeX cases environment is not correctly compiled since
> there is no line break after the first line in the pdf output, but in the
> html output (using mathjax) there is.
> 
> Here an example:
> 
> \f[
> x=\begin{cases}
> a & \varepsilon=0\\
> b & \varepsilon=1\\
> c & \varepsilon=2
> \end{cases}
> \f]
> 
> Happy to file a bug if needed. Just give me a shout.

Yes, please do, and please attach a self-contained example (source+config file in zip or tar) to the bug report 
so it easy for me to reproduce.

Regards,
  Dimitri

Re: [Doxygen-users] epstopdf: command not found ON MAC MAVERICKS

[Dimitri v. H. <do...@gm...>]

Hi Michael,

On 20 Dec 2013, at 0:43 , Michael Powell <mpo...@co...> wrote:

> Hello,
> 	I am using DOxygen to document an iPhone application. The context is Mac OS 10.9.1 with DOxygen 1.8.5. I got the TEX package from MacTEX. It's in a TEX subfolder to Applications and the release level on LaTeXiT is 2.5.4.
> 	When I use the DOxygen Wizard to "Run doxygen", I get the following error message with (cursory impression) every class:
> "sh: epstopdf: command not found
> error: Problems running epstopdf. Check your TeX installation!"
> 	This topic is not a new one, but I can't see from a Google search how to make it stop.
> 	If one looks, there is some mention of epstopdf down there (/usr/local/texlive/2013/texmf-dist/scripts/epstopdf/epstopdf.pl), but I'm enough of a Neanderthal that I can't judge whether that's enough, or how DOxygen should know how to find it (if it doesn't already know).

I'm not 100% sure this is the same epstopdf (mine came with macports and is located here /opt/local/libexec/texlive/binaries/epstopdf).
You could make a symlink to it by running the following in a terminal:

sudo ln -s /usr/local/texlive/2013/texmf-dist/scripts/epstopdf/epstopdf.pl /usr/local/bin/epstopdf

Then running 'epstopdf --version' in the terminal should print some version info.
Once that works, doxygen will probably also be able to find it.

Regards,
  Dimitri

[Doxygen-users] LaTeX environment cases: no line break

[Jannick <jan...@gm...>]

It appears the the LaTeX cases environment is not correctly compiled since
there is no line break after the first line in the pdf output, but in the
html output (using mathjax) there is.

Here an example:

\f[
x=\begin{cases}
a & \varepsilon=0\\
b & \varepsilon=1\\
c & \varepsilon=2
\end{cases}
\f]

Happy to file a bug if needed. Just give me a shout.

Many thanks.
J.

Re: [Doxygen-users] Escaping period character (.)

[Brian B. <Bri...@Ve...>]

For those who are interested, just keep adding backslash characters one at a
time and testing each until it displays correctly. This version finally
worked in my case:

...sent to the trigger by AccuRev to
<tt>\%ACCUREV_HOME\%\\\\\\\\.accurev\\Param\\<trigger-command-principal-timestamp\>.xml</tt>
on the machine where the trigger process runs. 

Thanks,
Brian




--
View this message in context: http://doxygen.10944.n7.nabble.com/Escaping-period-character-tp3545p6415.html
Sent from the Doxygen - Users mailing list archive at Nabble.com.

[Doxygen-users] Segfault when using tag files from documentation that has been compiled using tag files

[JohnOldman <j.r...@wa...>]

Hi,

I've recently switched from doxygen 1.6.1 to 1.8.5 (I have updates my
configuration files) and now have the following issue.
I am compiling documentation for a project, which I am separating into a
number of different components. The project also uses a number of third
party libraries.
So first I compile the documentation for the third party libraries and
create tag files. Then I compile the documentation for the components in the
order following dependencies, both reading and writing tag files in the
process. For the first component there is no issue. But as soon as I am
reading in a tag file that was generated compiling a documentation which in
turn uses tag files, I get a segfault. I have tested this many times and
have isolated the issue to that. Just to make this clear:

Compile documentation for (using tpl for third party libaries and comp for
components)
tpl1, write tag file OK
tpl2, write tag file OK
comp1, read tag files for tpl1,tpl2, write tagfile OK
comp2, read tag files for tpl1,tpl2,comp1 SEGFAULT

The last few lines of output I get from doxygen are
Building page list...
Search for main page...
Computing page relations...
Determining the scope of groups...
Sorting lists...
Freeing entry tree
Determining which enums are documented
Computing member relations...
Building full member lists recursively...
Adding members to member groups.
Computing member references...
Inheriting documentation...
Generating disk names...
Adding source references...
Adding xrefitems...
Segmentation fault

Does anyone have an idea what I can do about this?
Thanks
Jan



--
View this message in context: http://doxygen.10944.n7.nabble.com/Segfault-when-using-tag-files-from-documentation-that-has-been-compiled-using-tag-files-tp6414.html
Sent from the Doxygen - Users mailing list archive at Nabble.com.

[Doxygen-users] epstopdf: command not found ON MAC MAVERICKS

[Michael P. <mpo...@co...>]

Hello,
	I am using DOxygen to document an iPhone application. The context is Mac OS 10.9.1 with DOxygen 1.8.5. I got the TEX package from MacTEX. It's in a TEX subfolder to Applications and the release level on LaTeXiT is 2.5.4.
	When I use the DOxygen Wizard to "Run doxygen", I get the following error message with (cursory impression) every class:
"sh: epstopdf: command not found
error: Problems running epstopdf. Check your TeX installation!"
	This topic is not a new one, but I can't see from a Google search how to make it stop.
	If one looks, there is some mention of epstopdf down there (/usr/local/texlive/2013/texmf-dist/scripts/epstopdf/epstopdf.pl), but I'm enough of a Neanderthal that I can't judge whether that's enough, or how DOxygen should know how to find it (if it doesn't already know).

Regards,
Michael Powell
P. O. Box 567
Boulder Creek, CA 95006
(408) 529-0864 (mobile)
mpo...@co...
http://home.comcast.net/~mpowell-programming
http://www.linkedin.com/in/michaelhpowell

[Doxygen-users] Docbook xml output not getting Detailed Description

[<rus...@ve...>]

Hi,

I have a Doxygen config already defined. If i generate html or straight xml, for a given function call, the brief and detailed description is included. When i try and generate DocBook xml from the same configuration, i get the function call, but i DONT get the brief or detailed description info. This also causes a broken link to references of this.

For Example i have the following first few lines, in the source .h file:

/**
* @brief       Provides interface to run PSCON self tests
*
* @description contains the logic to place the PSCON diagnostic compare block in a self-test mode in order\n
* to test the * failsafe feature. Three diagnostic features are supported by this API.

In the html version of the _8h.html generated from the source api, i get the following:

<p>Provides interface to run PSCON self tests. </p>
<dl class="section user"><dt>Description:</dt><dd>contains the logic to place the PSCON diagnostic compare block in a self-test mode in order<br/>
 to test the * failsafe feature. Three diagnostic features are supported by this API.<br/> 

In the plain xml version i get the following:

<briefdescription>
<para>Provides interface to run PSCON self tests. </para>        </briefdescription>
    <detaileddescription>
 <para><simplesect kind="par"><title>Description:</title><para>contains the logic to place the PSCON diagnostic compare block in a self-test mode in order<linebreak/>
 to test the * failsafe feature. Three diagnostic features are supported by this API.<linebreak/> 

In the DocBook xml generated version of this i only get the function call and its parameters. NO descriptions, brief or otherwise, are generated. I have double checked and i have both brief and detailed descriptions checked in my config.

This is my first time using doxygen to generate DocBook xml. Is this a known issue? Is there a setting i may have overlooked?

Any help is greatly appreciated!

Thanks,

Re: [Doxygen-users] PHP alternative syntax (SOLVED)

[Willem B. <w-...@dd...>]

> Doxygen has a pre-processor similar to the C/C++ pre-processor.  Is your
> Doxygen configuration, you can configure "macros" to replace the
> alternate keywords with their primary equivalents.

I wrote a little batch file (translate.sh) that calls "sed -f phpalt.sed $1"

And phpalt.sed contains:
/^\s*if\s*[(]/s/\:$/\{/
/^\s*while\s*[(]/s/\:$/\{/
/^\s*for\s*[(]/s/\:$/\{/
/^\s*foreach\s*[(]/s/\:$/\{/
/^\s*switch\s*[(]/s/\:$/\{/
/^\s*else:/s/else:/\}else\{/
/^\s*elseif\s*[(]/s/elseif/\}elseif/
s/endif;/\}/
s/endwhile;/\}/
s/endfor;/\}/
s/endforeach;/\}/
s/endswitch;/\}/

and set FILTER_PATTERNS to the value *.php=translate.sh

That seems to do the trick.

Thanks.

Re: [Doxygen-users] PHP alternative syntax

[Albert <alb...@gm...>]

Dear Ron, Willem,

When the words are keywords defined in the php standard (I don't know php I
don't know about the keywords officially defined) it has advantages to
place them in the lex code (e.g. code coloring).

Albert


On Wed, Dec 18, 2013 at 5:20 PM, Ron Wilson <ron...@gm...> wrote:

>
> On Wed, Dec 18, 2013 at 8:44 AM, <
> dox...@li...> wrote:
>
>>
>> Date: Wed, 18 Dec 2013 14:22:25 +0100
>> From: Willem Bogaerts <w-...@dd...>
>> Subject: [Doxygen-users] PHP alternative syntax
>> To: dox...@li...
>> Message-ID: <52B...@dd...>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>>
>> Dear group,
>>
>> Does anyone know where I can find the PHP keywords in the doxygen source
>> code? I'd like to add the "alternative syntax" ending keywords, like
>> "endif", "endforeach", "endwhile", etc.
>>
>
> Doxygen has a pre-processor similar to the C/C++ pre-processor.  Is your
> Doxygen configuration, you can configure "macros" to replace the alternate
> keywords with their primary equivalents.
>
> Alternately, you could write an input filter for Doxygen to perform the
> replacements. You could even write the filter in PHP.
>
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
> Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>
>

Re: [Doxygen-users] PHP alternative syntax

[Ron W. <ron...@gm...>]

On Wed, Dec 18, 2013 at 8:44 AM, <
dox...@li...> wrote:

>
> Date: Wed, 18 Dec 2013 14:22:25 +0100
> From: Willem Bogaerts <w-...@dd...>
> Subject: [Doxygen-users] PHP alternative syntax
> To: dox...@li...
> Message-ID: <52B...@dd...>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Dear group,
>
> Does anyone know where I can find the PHP keywords in the doxygen source
> code? I'd like to add the "alternative syntax" ending keywords, like
> "endif", "endforeach", "endwhile", etc.
>

Doxygen has a pre-processor similar to the C/C++ pre-processor.  Is your
Doxygen configuration, you can configure "macros" to replace the alternate
keywords with their primary equivalents.

Alternately, you could write an input filter for Doxygen to perform the
replacements. You could even write the filter in PHP.

Re: [Doxygen-users] PHP alternative syntax

[Albert <alb...@gm...>]

Dear Willem,

Please have a look at code.l and scanner.l (are used for multiple
languages).

Albert



On Wed, Dec 18, 2013 at 2:22 PM, Willem Bogaerts <w-...@dd...> wrote:

> Dear group,
>
> Does anyone know where I can find the PHP keywords in the doxygen source
> code? I'd like to add the "alternative syntax" ending keywords, like
> "endif", "endforeach", "endwhile", etc.
>
> This should prevent those keywords to be mistaken for functions and to
> be added as references.
>
> Thanks in advance,
>
> Willem.
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
> Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>

[Doxygen-users] PHP alternative syntax

[Willem B. <w-...@dd...>]

Dear group,

Does anyone know where I can find the PHP keywords in the doxygen source
code? I'd like to add the "alternative syntax" ending keywords, like
"endif", "endforeach", "endwhile", etc.

This should prevent those keywords to be mistaken for functions and to
be added as references.

Thanks in advance,

Willem.