| Anonymous | Login | Signup for a new account | 10-31-2025 04:51 PDT | 
| Main | My View | View Issues | Change Log | Docs | 
| Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0002935 | [Quercus] | minor | always | 09-14-08 12:57 | 09-15-08 16:06 | ||||
| Reporter | koreth | View Status | public | ||||||
| Assigned To | ferg | ||||||||
| Priority | normal | Resolution | fixed | Platform | |||||
| Status | closed | OS | |||||||
| Projection | none | OS Version | |||||||
| ETA | none | Fixed in Version | 3.2.1 | Product Version | 3.2.1 | ||||
| Product Build | |||||||||
| 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 | |||||||||
| Attached Files | |||||||||
|  | |||||||||
| Mantis 1.0.0rc3[^]
	Copyright © 2000 - 2005 Mantis Group
	29 total queries executed. 26 unique queries executed. |