GNOME Bugzilla – Bug 667835
HEREDOC still not working
Last modified: 2012-02-25 15:37:12 UTC
I am using CentOS if that helps. I downloaded the binaries of 1.7.6.1. I have a folder of 25 files. One of these files contains a lot of HEREDOC. It never parses the class (or any methods of the class) in this file. A sample is below: class UserModel { public function sendUpdatedEmailAddressEmail($activation_token) { $url = "http://{$_SERVER['SERVER_NAME']}/activate/" . $this->getUserId() . "?token=$activation_token"; $copyrightyear = date('Y'); $message_text = <<<MESSAGE Dear Comic Enthusiast, You have changed your email address at comiXology.com! Please note - you must complete this last step to confirm your email address. You will only need to click on the link once, and your account will be activated. To complete this last step, click on the link below: $url If you are having problems please contact a member of our support staff at info@comixology.com. Regards, The comiXology Development Team. Express yourself, users can now write reviews of their favorite items. http://www.comixology.com/reviews/ Got an iPhone? Now you can view your comiXology pull list anywhere and everywhere. http://www.comixology.com/iphone/ © $copyrightyear Iconology, Inc. MESSAGE; return $mail->Send(); } } I left out a lot of code for the sake of brevity. But removing all of the HEREDOC causes it to work perfectly.
It does 100% properly process all the other files (none of which have HEREDOC). Again, if I remove all the HEREDOC in the file, it works perfectly, parsing all of the methods (including the ones where the HEREDOC was written).
Hi Shawn, I was not able to reproduce the problem with your example. That said, the HEREDOC contents was not properly skipped. I'll correct this. If you could attach a self-contained example (source+config file in a tar or zip) that allows me to reproduce the problem, I can test if my solution works.
This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.8.0. 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.