Spellscript Bugs
From Hack/Mine Wiki
(Difference between revisions)
m (→0.6.4.2) |
|||
| Line 22: | Line 22: | ||
! Catchy Title || Status || Single/Multiplayer || Description, Error Message(s) | ! Catchy Title || Status || Single/Multiplayer || Description, Error Message(s) | ||
|- | |- | ||
| − | | Non-working Closures || | + | | Non-working Closures || In-Progress || Both || Function pointers don't properly maintain a reference to their "closure"-- this means that if a function is invoked as a function pointer in a different scope than it was originally declared, then references to variables ''outside'' the scope of the function from ''within'' the function will likely result in errors. Again, this depends on where the function pointer is invoked, meaning the errors may be subtle and difficult to find! |
In the next update, references to variables within a function pointer's closure will either be fixed or removed (though possibly reintroduced later). If not removed, then it may be required that references to external variables only be possible for ''constant'' variables (a feature yet to be introduced to Spellscript), in a similar vein as Java's anonymous inner classes' "closures". | In the next update, references to variables within a function pointer's closure will either be fixed or removed (though possibly reintroduced later). If not removed, then it may be required that references to external variables only be possible for ''constant'' variables (a feature yet to be introduced to Spellscript), in a similar vein as Java's anonymous inner classes' "closures". | ||
Revision as of 09:17, 10 March 2013
The following is a list of known Spellscript bugs, according to version. Please add bugs to the list as you find them, and try to make entries informative and brief. Details such as the error message, a script triggering the error, and even images are invaluable to solving the issue. Finally, set "Dev Status" to "Open" when first creating the entry (the devs will change its value as they address the issue).
If anything is subject to debate, please use the Discussion Page to sort it out rather than edit warring. (You can reflect this contention in the bug's description.)
Contents |
Legend
| Status | Meaning |
|---|---|
| Open | Devs have yet to address the issue. |
| Unconfirmed | Devs need more details to address the issue. |
| In-Progress | Devs are working on it. |
| Pending | Something nasty is preventing a fix by the next update. |
| Fixed | Devs have fixed the issue, and the fix will be out in the next update. |
0.6.4.2
| Catchy Title | Status | Single/Multiplayer | Description, Error Message(s) |
|---|---|---|---|
| Non-working Closures | In-Progress | Both | Function pointers don't properly maintain a reference to their "closure"-- this means that if a function is invoked as a function pointer in a different scope than it was originally declared, then references to variables outside the scope of the function from within the function will likely result in errors. Again, this depends on where the function pointer is invoked, meaning the errors may be subtle and difficult to find!
In the next update, references to variables within a function pointer's closure will either be fixed or removed (though possibly reintroduced later). If not removed, then it may be required that references to external variables only be possible for constant variables (a feature yet to be introduced to Spellscript), in a similar vein as Java's anonymous inner classes' "closures". |
0.6.4.1
| Catchy Title | Status | Single/Multiplayer | Description, Error Message(s) |
|---|---|---|---|
| SERVER Network Propagation | Fixed | SMP | Serialization error when the SERVER global variable is transmitted over the network in any fashion-- results in scripts only being executed on the server side, rather than both client and server. This results in strange behavior. |
0.6.4.0
| Catchy Title | Status | Single/Multiplayer | Description, Error Message(s) |
|---|---|---|---|
| Many-Type Inference w/ Classes | Fixed | Both | Type inference of multiple expressions causes a StackOverflow error if they evaluate to class-types (list instantiations, return type inference, etc) |
| Multifield Declaration Issues | Fixed | Both | Multifield declarations in class declarations cause a myriad of issues involving stackframe sizes-- don't use them! |
| Non-Parameterless Constructors | Fixed | Both | Constructors accepting more than the "self" parameter incorrectly resolve the parameter types, causing an invalid error. |
| "server" is None | Fixed | SMP | "server" is None in Schedulable Scripts. |
