From: SourceForge.net <no...@so...> - 2003-04-11 06:40:42
|
Bugs item #719504, was opened at 2003-04-11 02:57 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=438935&aid=719504&group_id=44253 Category: DynamicJava Group: Annoying Status: Open Resolution: None Priority: 5 Submitted By: Geoff Oakham (oakhamg) Assigned to: Nobody/Anonymous (nobody) Summary: Interfaces & return types Initial Comment: [200...@mb...] Hi there, This year, the instructors are U of T choose DrJava as the 'official ide' and it's been a success. The only snag we hit was with type assignments (as mentioned in the drjava FAQ.. at least, I think it's the same issue). What's happening is students are submitting: public foo implements Iterator { // ... String next () { //... } //... } where the regular compiler (which we use during testing) wants: public foo implements Iterator { // ... Object next () { //... } //... } I know this artifact is a 'feature' of DynamicJava and isn't your code (or fault), but I was wondering if I could submit the issue as a feature request for a work-around or a bug report to disable some DynamicJava 'features'. A possible work-around could be an option to compile & run the code using the 'real' compiler and vm. I know this could disable the interactions pane.. but that shouldn't be a big deal. Anyways, just wanted to run this by you before I submitted anything on SourceForge. Thanks for your time, Geoff ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=438935&aid=719504&group_id=44253 |