headers
FJTC (Fabio Jun Takada Chino | 1 Jul 2004 02:34
Picon
Favicon

Brazilian Portuguese update

Hi there.

I'm sending the latest version of the Brazilian Portuguese translator. I 
know I'm a bit late but I miss the last developer messages because I 
moved my e-mail address from the university account to a paid account 
last month (I forgot to register my new account in this list).

See you
FJTC
Attachment (translator_br.h.bz2): application/x-bzip2, 8 KiB
Permalink | Reply | 0 comments |
headers
Paul.Ross | 7 Jul 2004 13:37
Favicon

Case sensitivity of #include's

Running on Windoze if you have #include "foo.h" but the file is named 
"FOO.H" then Doxygen's preprocessor silently ignores the include and thus 
can miss declarations. I realise that this use of #include is poor 
programming practice and that this issue has been discussed here before 
and the decision was made not to support bad practice.

However it would be very useful (for me at least) if a warning was written 
into the log so that the source code could be fixed. Alternatively have a 
configurable flag that will include the correct file on case insensitive 
OSs.

The problem is that although I have narrowed where this is happening down 
I can't see a work around so any advice would be greatly appreciated. So 
far I have (using Doxygen 1.3.7):
In pre.l 1029 the function:
readIncludeFile(const QCString &inc)
The call at line 1056:
    if ((f=findFile(incFileName,localInclude)))
Under Windows this return non-null even if the case of the file name is 
wrong, however at line 1092 this call silently fails and I can't see why:
    preYYin=f;
    yy_switch_to_buffer(yy_create_buffer(preYYin, YY_BUF_SIZE));

I am not familiar with FLEX and I can't see what is going on in there, the 
MS Visual C++ debugger is of little help either.

Any advice gratefully received, thanks in advance!

Regards,
(Continue reading)

Permalink | Reply | 0 comments |
headers
Petr Prikryl | 8 Jul 2004 07:31
Picon

Windows binaries available for Doxygen-1.3.7-20040704 in CVS

Hi,

If interested, you can download the doxygen binaries
compiled for MS Windows from

  http://doxygen.sourceforge.net/dl/doxygen-1.3-cvs/

This is the place where you should find also the next
releases.  The name of the archive is constructed 
from the date of CVS release and looks like
doxygen_win32_2004mmdd.zip, where mm and dd is
month and day of releasing the version.

The binaries are NOT created automatically, so it may
happen that some newer CVS sources were not compiled
because I am not present to do that or I forgot... ;)

Regards,
    Petr

P.S. The translator report can be found in the file 
     like tr2004mmdd.zip.

--

-- 
Petr Prikryl (prikrylp at skil dot cz)

-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches,
(Continue reading)

Permalink | Reply | 0 comments |
headers
Enno Bartels | 11 Jul 2004 19:37
Picon
Favicon

CVS .cvsignore files created

Hi

I am working with the cvs version of
doxygen at the moment.
Everytime I do a cvs up after compiling
I get some this output

? .makeconfig
? .tmakeconfig
? Makefile
? addon/doxmlparser/examples/metrics/Makefile
? addon/doxmlparser/examples/metrics/metrics.pro
? addon/doxmlparser/src/Makefile
? addon/doxmlparser/src/doxmlparser.pro
? addon/doxmlparser/test/Makefile
? addon/doxmlparser/test/xmlparse.pro
? addon/doxywizard/Makefile
? addon/doxywizard/doxywizard.pro
? doc/Makefile
? examples/Makefile
? libmd5/Makefile
? libmd5/libmd5.pro
? libpng/Makefile
? libpng/libpng.pro
? qtools/Makefile
? qtools/qtools.pro
? src/Makefile
? src/doxygen.pro
? src/doxytag.pro
? src/libdoxycfg.pro
(Continue reading)

Permalink | Reply | 0 comments |
headers
Enrico Maasch | 23 Jul 2004 22:07
Picon

unresolved symbols while building on windows+nmake

Hi,

I have found 'doxygen' on a friends computer. Now, while starting a 
serious programin project, I thinked to use this nice tool,too. After 
learning the fundamental use and considering the comands included the 
doxygen-language, I had missed some few features.

How about that:
    \xparam a free labeling \param block inspired by \xrefitem - i like 
the <dl>-style of a \param section
    \vval called 'valid values', an implementation of  \xparam to 
describe the valid intended values for an attribute
    (i.e 'align' has the valid values (0,1,2,3), handled by appropriate 
macros ('left', 'right', 'center', 'justified'))

I have taken the source from CVS an started the build process by 
invoking the provided batch file

    make.bat msvc

Naturally, I have considered all given recomendations of the install 
guide from doxygens doc.

But, there are any unresolved symbols when linking, when recompiling 
with the Doxygen-Project from within MS VC 6 too.

Here is the dump from the Output-Window. Nmake, called via make.bat at 
commandline prompt, will stop immediately after finding the first 
'unresolved'-error. (sorry for german messages ;-)
(Continue reading)

Permalink | Reply | 1 comment |
headers
Dimitri van Heesch | 25 Jul 2004 16:06
Picon
Favicon

Re: unresolved symbols while building on windows+nmake

On Fri, Jul 23, 2004 at 10:07:27PM +0200, Enrico Maasch wrote:
> Hi,
> 
> I have found 'doxygen' on a friends computer. Now, while starting a 
> serious programin project, I thinked to use this nice tool,too. After 
> learning the fundamental use and considering the comands included the 
> doxygen-language, I had missed some few features.
> 
> How about that:
>    \xparam a free labeling \param block inspired by \xrefitem - i like 
> the <dl>-style of a \param section

Could be useful indeed, if it cannot be made with ALIASES and/or 
\par already that is.

>    \vval called 'valid values', an implementation of  \xparam to 
> describe the valid intended values for an attribute
>    (i.e 'align' has the valid values (0,1,2,3), handled by appropriate 
> macros ('left', 'right', 'center', 'justified'))

I would call this \range, but it may be useful indeed (at least I often
find this missing in the documentation of a parameter).

> I have taken the source from CVS an started the build process by 
> invoking the provided batch file
> 
>    make.bat msvc
> 
> Naturally, I have considered all given recomendations of the install 
> guide from doxygens doc.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Adam Treat | 28 Jul 2004 11:12
Picon
Favicon

Patch for Q_PROPERTY read and write accessor method names in XML

Hello,

I have created a patch for doxygen that encapsulates the read and write 
accessor method names in doxygen xml output.  This addresses the thorny 
problem where the read accessor name does not match the actual method name.

Examples:

Q_PROPERTY( bool exclusiveToggle READ isExclusiveToggle )
        * has "is" appended to read method

Q_PROPERTY( ToggleState toggleState READ state )
        * read method does not include "toggle"

Q_PROPERTY( int selectedId READ selectedId WRITE setButton )
        * write method substantially differs from property name

The patch is minimally intrusive.

Adam Treat
Attachment (patch.diff): text/x-diff, 5745 bytes
Permalink | Reply | 0 comments |
headers
Arend van Beelen jr. | 30 Jul 2004 17:24
Picon

PHP5 patch

Hi!

Attached you find a small patch to support some of the new 
PHP5 features, like real public, protected and private 
members and interfaces. Without the patch Doxygen 
currently pretty much chokes on PHP5 if protection 
keywords are specified.

Greets,
Arend jr.

--
Arend van Beelen jr.
http://www.liacs.nl/~dvbeelen
Attachment (php5.patch): application/octet-stream, 1503 bytes
Permalink | Reply | 0 comments |

Gmane