Re: JavaC compilation error: '.' expected
Steve Wampler wrote:
Klauer wrote:
Well, I'll try my best to describe the package structure.
We have a set of pre-compiled .class files that sit on a client and
server of our software on the hard drive. These supporting .class
files are generated by that program itself, and we pull reference and
import these directly from those physical locations. They do fall
under a package, as defined in their .java, but physically--on the
hard drive--they sit in a random directory, e.g. client/module1/
runtime/classes.
With the way we had it working before, this is an example of what most
of the extending java modules would look like:
package com.company.name.package.one;
import crClass;
public class crExtClass
{
...
}
I think the rule about not being able to import classes from the default
package into classes in named packages may have existed in 1.3. See the
reference in the previous posting to Roedy's Java Glossary for details.
We do realize that Java 1.3 is obsolete, don't we? In addition to 1.3 being
three major versions old, Sun took it off life support last year. In fact,
Java 1.4 is already in its end-of-life process. It's probably worth upgrading.
Also, to the OP, please do not top post, and your question would be a lot
easier if you'd provide a short, self-contained complete (compilable) example
(SSCCE) that illustrates the difficulty. If you were to COPY and PASTE the
error message instead of waving your hands with some "etc.etc. [sic]"
mumbo-jumbo people could help better. Accurate answers can only come from
accurate information.
BTW, the tool is "javac", not "JavaC". Computers are picky about that sort of
thing.
--
Lew