tifacts. This is one PITA that is preventing my Mavenization
> efforts a little.
>
> Chris
>
>
> Von: Michael Schmalle
> Gesendet: Dienstag, 19. Mai 2015 11:46
> An: dev@flex.apache.org
> Betreff: Re: [Falcon] ASDocTokenizer and RawA
is one PITA that is preventing my Mavenization
> efforts a little.
>
> Chris
>
>
> Von: Michael Schmalle
> Gesendet: Dienstag, 19. Mai 2015 11:46
> An: dev@flex.apache.org
> Betreff: Re: [Falcon] ASDocTokenizer and RawASDocTokeni
2015 11:46
An: dev@flex.apache.org
Betreff: Re: [Falcon] ASDocTokenizer and RawASDocTokenizer JFlex deps
Yes it makes sense to me but in no way right now am I capable to even look
at that code. I only have bits of spare time and getting back into Antlr,
especially a new version would have to be
in there ... I was always planning on continuing the work as
> soon as I could have a working test-suite.
>
> Chris
>
> ________
> Von: Michael Schmalle
> Gesendet: Sonntag, 17. Mai 2015 20:29
> An: dev@flex.apache.org
> Betreff: Re: [Falcon] ASDocTokenizer and RawASDocT
15 20:29
An: dev@flex.apache.org
Betreff: Re: [Falcon] ASDocTokenizer and RawASDocTokenizer JFlex deps
I actually have a grammar I used for ASDocs years ago, check it out. I was
actually looking at that last night when I hit the JFlex problem.
I think the grammar I created used Antlr 3 but we coul
... what do you think?
>
> Chris
>
> -Ursprüngliche Nachricht-
> Von: Michael Schmalle [mailto:teotigraphix...@gmail.com]
> Gesendet: Sonntag, 17. Mai 2015 00:20
> An: dev@flex.apache.org
> Betreff: Re: [Falcon] ASDocTokenizer and RawASDocTokenizer JFlex deps
>
> No, th
]
Gesendet: Sonntag, 17. Mai 2015 00:20
An: dev@flex.apache.org
Betreff: Re: [Falcon] ASDocTokenizer and RawASDocTokenizer JFlex deps
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
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
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
som
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
10 matches
Mail list logo
