Announcement

Collapse
No announcement yet.

4dcompiler.exe has stopped working (Diablo,Visi,Designer,4.4.0.10b, others?)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • 4dcompiler.exe has stopped working (Diablo,Visi,Designer,4.4.0.10b, others?)

    I hope this post helps someone with a similar issue. Windows reported "4dcompiler.exe has stopped working" The problem was that I was accessing a private, multi-word (array) variable with the same name as a global multi-word variable. Here's the gist of it...

    var bar[2];
    ...

    func foo()
    var private bar[2];
    ...
    endfunc

    //So far, so good, however, on the first access of foo.bar the compiler was locking up...

    ...
    foo.bar[0]:=bar[0]; //you're dead
    ...

    //Note: simple single-word variables with the same name do not exhibit this behavior.

    Ok, that's it. I want to thank the guys at 4D Systems for identifying this for me, so thanks guys! I'm a Yuuuuge fan.

    G
Working...
X