Menu

#251 Error on interactions package/import typo

open
nobody
5
2005-02-28
2005-02-28
Dan Smith
No

If I type

import mypackage.mysubpackag.*

(having mispelled "mysubpackage") in the interactions pane, there is
no signal that I've made a mistake. I would propose defining any
package or import statement

package <PATH>;

or

import <PATH>.*;

where <PATH> refers to a package that does not exist (according to
the classpath) as an error.

Discussion

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.