Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AVM2 special operations not detected #727

Open
hydroper opened this issue Jan 5, 2024 · 1 comment
Open

AVM2 special operations not detected #727

hydroper opened this issue Jan 5, 2024 · 1 comment

Comments

@hydroper
Copy link

hydroper commented Jan 5, 2024

Errors such as:

Definition avm2.intrinsics.memory.li32 could not be found.

occur using the avm2.intrinsics package. But the project compiles fine with asconfigc; any idea?

Here's my asconfigc.json:

{
    "config": "air",
    "type": "app",
    "files": [
        "src/org/agera/crypto/worker/CryptoWorker.as"
    ],
    "application": "app.xml",
    "compilerOptions": {
        "debug": true,
        "omit-trace-statements": false,
        "source-path": ["src"],
        "library-path": ["libs"],
        "output": "build/org.agera.crypto.worker.swf"
    }
}
@joshtynjala
Copy link
Member

as3mxml-vscode's cod intelligence doesn't necessarily use the same compiler that gets called by asconfigc, so that's why you see it succeed with asconfigc, but see an error in VSCode. It appears that vscode-as3mxml doesn't know how to find the avm2.intrinsics package. I would have assumed that it's defined in playerglobal.swc (or another .swc) in the SDK, but perhaps not. Maybe Adobe's ASC 2.0 compiler hard-codes these functions. If that's the case, then the Royale compiler used by vscode-as3mxml would need to be modified to support them.

Regardless, it is safe to ignore the error for now, since asconfigc compiles successfully.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants