After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 650397 - Can only use nine alias arguments
Can only use nine alias arguments
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
unspecified
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2011-05-17 14:31 UTC by tallen83
Modified: 2012-11-18 11:12 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description tallen83 2011-05-17 14:31:27 UTC
The documentation does not indicate an upper limit to the number of arguments available in an alias.

Expected:
Tag
@test{arg1=1,arg2=2,arg3=3,arg4=4,arg5=5,arg6=6,arg7=7,arg8=8,arg9=9,arg10=10}

AlIASES entry:
test{1}=@details\n(\@test=\1)\n \
test{2}=@details\n(\@test=\1,\2)\n \
test{3}=@details\n(\@test=\1,\2,\3)\n \
test{4}=@details\n(\@test=\1,\2,\3,\4)\n \
test{5}=@details\n(\@test=\1,\2,\3,\4,\5)\n \
test{6}=@details\n(\@test=\1,\2,\3,\4,\5,\6)\n \
test{7}=@details\n(\@test=\1,\2,\3,\4,\5,\6,\7)\n \
test{8}=@details\n(\@test=\1,\2,\3,\4,\5,\6,\7,\8)\n \
test{9}=@details\n(\@test=\1,\2,\3,\4,\5,\6,\7,\8,\9)\n \
test{9}=@details\n(\@test=\1,\2,\3,\4,\5,\6,\7,\8,\9,\10)\n \

When ten arguments are used it is expected that they all function.

Found:
When 10-19 arguments are used, they are replaced by the first argument. When 20-29 are used they are replaced by the second argument, etc..

The alias argument parsing, in the method 'replaceAliasArgument' on LN 6549 in util.cpp, should be iterated in reverse to capture alias arguments larger than a single digit.
Comment 1 Dimitri van Heesch 2011-06-05 14:35:36 UTC
Confirmed. Should be corrected in the next subversion update.
Comment 2 Dimitri van Heesch 2011-08-14 14:04:52 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.5. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant.