View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000765 | LDMud 3.5 | LPC Compiler/Preprocessor | public | 2010-11-22 23:19 | 2014-02-23 23:03 |
Reporter | zesstra | Assigned To | Gnomi | ||
Priority | normal | Severity | minor | Reproducibility | N/A |
Status | resolved | Resolution | fixed | ||
Target Version | 3.5.0 | Fixed in Version | 3.5.0 | ||
Summary | 0000765: Disallow the processing of void values | ||||
Description | During the discussion about bug 0000718 we came to the conclusion, that it is not sufficient to disallow only assignments of void values to variables, but we need to prevent any processing of them in expressions as well, e.g. (foo ? bar : void-fun) voidfun + non-void-value voidfun - non-void-value fun(voidfun); etc. pp. | ||||
Tags | No tags attached. | ||||
|
In the grammar there are only two things that have to be handled specially: function calls and comma expressions. So it might be a way to introduce two non-terminals voidexpr (maybe void) and nonvoidexpr (is not void). The problem is not to introduce ambiguities (as every voidexpr can be a nonvoidexpr, and every nonvoidexpr is alo a voidexpr). Perhaps we need some more non-terminals (a set classifying the origin (can or cannot be guaranteed non-void) and a set for the use (maybe void or must not be void)). |
|
Should be fixed with 0000721. |
Date Modified | Username | Field | Change |
---|---|---|---|
2010-11-22 23:19 | zesstra | New Issue | |
2010-11-22 23:19 | zesstra | Relationship added | parent of 0000718 |
2011-01-25 15:52 | Gnomi | Note Added: 0001961 | |
2014-02-23 22:56 | zesstra | Relationship added | related to 0000829 |
2014-02-23 23:02 | zesstra | Status | new => assigned |
2014-02-23 23:02 | zesstra | Assigned To | => Gnomi |
2014-02-23 23:03 | zesstra | Note Added: 0002234 | |
2014-02-23 23:03 | zesstra | Status | assigned => resolved |
2014-02-23 23:03 | zesstra | Fixed in Version | => 3.5.0 |
2014-02-23 23:03 | zesstra | Resolution | open => fixed |