|
Mantis - Quercus
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 2935 | minor | always | 09-14-08 12:57 | 09-15-08 16:06 | |
|
|
|||||
| Reporter: | koreth | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 3.2.1 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.2.1 | ||
|
|
|||||
| Summary: | 0002935: Java method is passed a Value in interpreted mode and a Var in compiled mode | ||||
| Description: |
If I have a Java method that takes a Value argument, then call it like MyJavaClass::method($foo); from PHP, in interpreted mode the argument is an instance of StringValue, DoubleValue, etc. Once the PHP file gets compiled, the argument is an instance of Var instead. Not a big deal since the Java code can do something like if (arg instanceof Var) { return method(((Var)arg).toValue()); } but it seems to be a recent behavior change; I don't remember seeing this before. Maybe it is perfectly legitimate to get passed a Var for pass-by-reference and the interpreted-mode behavior is incorrect, but it should at least be consistent between the two modes. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||