theprojecter / visdoc Goto Github PK

What steps will reproduce the problem?
Given the following AS2 code:

/**
 * Returns whether an exception was thrown within a callback
 * @param args Array The arguments passed to the callback function
 * @example  <code>
    trace('Error: ' + somevariable);
</code>

The output in the html file for the trace line will be:
<span class="codeIdentifier">trace</span>(&#<span 
class="codeNumber">39</span>;<span class="codeIdentifier">Error</span>: &#<span 
class="codeNumber">39</span>; + somevariable);

This causes the line to appear as "trace(&#39;Error: &#39; + somevariable); in 
the browser.

What version of the product are you using? On what operating system?
latest revision

What steps will reproduce the problem?
From the visdoc directory, ./VisDoc.pl -doc-sources {source dir} -output 
{output dir}

What is the expected output? What do you see instead?
During parsing the following error messages are output:
"Deep recursion on subroutine "VisDoc::ParserBase::_parseMethods" at 
/opt/visdoc/lib/VisDoc/ParserBase.pm line 642."
"Deep recursion on subroutine "VisDoc::ParserAS2::_swapPropertyGetSetters" at 
/opt/visdoc/lib/VisDoc/ParserAS2.pm line 441."

What version of the product are you using? On what operating system?
running r112 on Ubuntu 10.04 (Lucid Lynx)

Please provide any additional information below.

What steps will reproduce the problem?
1. Install Visdoc and Visdoc Tools
2. Add a file to the queue
3. Click 'Process'

What is the expected output? What do you see instead?

Expected: Visdoc will output documentation to the specified output folder

Actual: Visdoc stalls on the 'Processing' dialog

What version of the product are you using? On what operating system?

r112 from SVN. Mac OSX 10.6.4

Please provide any additional information below.

I see on the home page that this is a known issue. I was wondering if there is 
a way to manually install the Visdoc tools as a temporary work around..?

What steps will reproduce the problem?
When creating doc for something with multiple classpaths, the newer versions of 
VisDoc don't organize the classes the same.

Using r112 on Ubuntu 10.04 will give the output shown in:
"Bad Classpath sorting.jpg"

You will notice that all classes are shown at the same level, there is no 
organization of the classes by path.

Compare that to the output from an older version running on a Mac (OsX).  See 
"Good Classpath sorting.jpg"

Using earlier version (for example r8) on the Ubuntu system will correctly 
organize the classes by classpath.

https://github.com/ArthurClemens/VisDoc

What steps will reproduce the problem?
From the visdoc directory,
./VisDoc.pl -doc-sources {your source dir} -output {an output dir} 

When the parsing starts, you receive the message (assuming visdoc is located at 
/opt/visdoc):
Use of uninitialized value in string eq at /opt/visdoc/lib/VisDoc/ParserAS2.pm 
line 368.

What version of the product are you using? On what operating system?
using version r112 running on Ubuntu 10.04 (Lucid Lynx)

Please provide any additional information below.
Processing still continues and seems to finish without any issues.  Just a 
weird message.