For example change this:
add f2.r, f1.a
add f2.g, f1.a

to this:
add f2.rg, f1.aa

I can change PB-asm code and compile it again with apbj/dpbj, but having something like “PBV” will be really nice thing.

[as3v] ActionScript3 Verifier running …
[as3v] [Fatal Error] as3v3394498810895234175.log:1:1: Premature end of file.

problem as others, using AS3V in FDT with Ant. I actually found that _removing_ fork=”true” fixed the problem. I think that’s contrary to what’s said above, unless I misunderstood? Hopefully this might help anyone else with the same problem.

Thanks for a nice piece of kit :)

I went to Run/External Tools/Open External Tools Dialog/JRE Tab and checked “Run in the Workspace JRE”.

Hopefully this is useful to someone with similar problems.

[as3v] ActionScript3 Verifier running …
[as3v] [Fatal Error] as3v3394498810895234175.log:1:1: Premature end of file.

BUILD FAILED
C:\…\ant\as3v\build.xml:29: org.xml.sax.SAXParseException: Premature end of file.

I ran through FDT 3.1.1. Any ideas?

Can you tell me if the google code has been updated? I just checked it out but can’t find the rules package.

Cheers

Maybe a feature request on powerflasher’s Jira will help….

Great work BTW.

Anyways I am sorry that I could not continue the development and fix some bugs. Especially the FD integration is still on my plate. Work keeps me pretty busy at the moment.

I hope I will find some time during the next weeks.

Buildfile: C:\…\build.xml
main:
[as3v] ActionScript3 Verifier running …
[as3v] [Fatal Error] :-1:-1: Premature end of file.

BUILD FAILED
C:\…\build.xml:30: org.xml.sax.SAXParseException: Premature end of file.

Total time: 1 second

Any way of figuring out what file it is choking on? I have like 20 or 30 .as files now I think.

Do not check out the code — it is completly out of date. I will update the repository on Monday.

As far as FlashDevelop is concerned, a JAR will be perfectly fine, but I’m curious about the JNI suggestion: do you mean a DLL?

Now for FlashDevelop we can make a version really quick. AS3V has been designed for embedding and custom project models. So therefore we can simply write a FD tool which fits your needs.

For a more generic version I will update the command line tool with two features:
- Customized output (e.g. %level %filename:%line:%column %message)
- Single file parsing

For FlashDevelop we could create an even better version using a JNI wrapper — if you want. For instance, the C++ library could make use of pipes. The handling could be even better. But that is just an option. If you do not think its feasable we could simply add a tool that works query based.

I will work on the command line version on Monday and put everything on GoogleCode if I can find the time. You or someone else could also contribute on the FD task if you are interested.

FlashDevelop (even if it’s .NET) keeps a lot of Java processes in memory using custom wrappers to use them in a query-based model: asc, fdb, fcsh and mxmlc. I am even proud of the hack used to keep mxmlc.jar in memory (this provides incremental compilation for free).

So if your tool does, like mxmlc.jar, provide a static main entry point (flex2.tools.Compiler.main) we could certainly integrate efficiently your tool.

I am not sure if a command line version makes that much sense for a couple of reasons:

- Initialization of ASC is time consuming
- Startup of Java is time consuming
- HotSpot will be time consuming

The better approach would be to keep an AS3V running and query it for information. I am not sure if this will integrate easy with FD but it is basically the same concept which tools like fdb use.

Not to forget that there is an even bigger problem. ASC is currently used in a way so that you do not have to load playerglobals.swc etc. This is fine with me currently since AS3V does no interprocedural analysis but it might change in the near future. This means basically that a command line version would have to compile always the complete dependency graph for your class and this is where it will get nasty. Although, I am not sure how they handle incremental compilation. Maybe that would be an option.

Right now I could implement the single-file option for FD but I think a query-based architecture would be better.

A filename as input is simple to automate for a command line tool.

A more friendly (ie. standart file:line:column) output would be nice.

Keep up the good work!

http://www.flashdevelop.org/community/viewtopic.php?f=4&t=5033