No, this has nothing to do with your code. I am using the ASDocTokenizer which uses the RawASDocTokenizer that is generated by JFlex.
I really doubt you have touched that class, all it does is call nextToken() on the JFlex scanner. It's the JFlex scanner that is hitting a loop while trying to end the scan of the doc comment. Mike On Sat, May 16, 2015 at 6:01 PM, Alex Harui <aha...@adobe.com> wrote: > I don’t remember which version is which, but IIRC, more recent Jflex was > licensed under Apache or a more permissive license where older ones > weren’t, so we opted to simply the bundling by going to a more recent > version. > > If you are getting a loop it is more likely a bug in our source exposed by > some new scenario that wasn’t around two years ago. > > -Alex > > On 5/16/15, 2:26 PM, "Michael Schmalle" <teotigraphix...@gmail.com> wrote: > > >Hi, > > > >I am going through a lot of my code, one in particular is a new version of > >the ASDoc tool that uses velocity templates. > > > >I know 2 years ago I was able to document the whole Flex SDK with the > >current code base. > > > >I noticed in the compiler downloads.xml the JFlex version was changed from > >1.5.1 to 1.6.0 by Erik. > > > >Was there a reason to update the version? I know dealing with > >parser/lexer/scanner generators it's not a good idea to update versions > >unless it's tested. > > > >Obviously the ASTokenizer that is used with the ASParser still seems to > >function correctly but the ASDocTokenizer is running into an infinite loop > >when it reaches the end of tokenizing the asdoc IE */. > > > >I changed the download version back to 1.5.1 and regenerated the scanner > >but I am still getting the loop where I had never had this problem before. > > > >I doubt anybody has answers but I was wondering if Alex might have any > >ideas to other things that changed in the dependencies. > > > >As it stands, maybe there is a bug in the grammar, I might check this out > >when I have time but it worked before. > > > >It seems that when Falcon was donated it used 1.5.1, so I am totally > >clueless as to what changed and why the infinite loop in ALL scanning. > > > >Mike > >
