-
I have noticed that the parser begins an infinite loop with memory allocation when a file is ended by a "//" comment. It happened under a windows OS using the command line prompt but I believe it is a general bug. After removing the comment (or copying it to another line that is not the last one) the parser seemed to work fine.
The bug is not present only with a // comment in the last line...
04:00PM UTC on Jul 27 2007 in PhpDocumentor
-
ecalot committed patchset 136 of module PR to the princed CVS repository, changing 1 files.
05:44AM UTC on Jul 31 2004 in princed
-
ecalot committed patchset 135 of module PR to the princed CVS repository, changing 2 files.
05:34AM UTC on Jul 31 2004 in princed
-
ecalot committed patchset 134 of module PR to the princed CVS repository, changing 2 files.
04:59AM UTC on Jul 31 2004 in princed
-
ecalot committed patchset 133 of module PR to the princed CVS repository, changing 1 files.
08:00PM UTC on Jul 30 2004 in princed
-
ecalot committed patchset 132 of module PR to the princed CVS repository, changing 1 files.
07:56PM UTC on Jul 30 2004 in princed
-
ecalot committed patchset 131 of module PR to the princed CVS repository, changing 1 files.
07:35PM UTC on Jul 30 2004 in princed
-
ecalot committed patchset 130 of module PR to the princed CVS repository, changing 1 files.
07:32PM UTC on Jul 30 2004 in princed
-
ecalot committed patchset 129 of module PR to the princed CVS repository, changing 2 files.
04:11AM UTC on Jul 30 2004 in princed
-
ecalot committed patchset 128 of module PR to the princed CVS repository, changing 7 files.
09:55AM UTC on Jul 06 2004 in princed
