can some tell me the difference between the import we use in java and the one in objective C?
+3
A:
In Java,
import long.package.name.Foo;tells the compiler that any timeFooappears as aa class name in the current source file, it really meanslong.package.name.Foo- so allimportreally does is allow you to write shorter source code. Finding class definitions is done via the convention of having class names match file names and package names match directory hierarchies.In Objective C, an
#importstatement is actually replaced with the contents of the imported file by the preprocessor, unless that file has already been imported (this is the difference between#importand the older#includedirective).
Michael Borgwardt
2010-09-30 07:51:16
Does it mean that in Java, instead of writing "long.package.name.Foo" to represent a Foo, import helps us in referring it shortly.
Krishnan
2010-09-30 07:58:37
@Krishnan: Yes, that's exactly what import does.
Michael Borgwardt
2010-09-30 08:02:27
and that is all that it does. No magical side effects (like Perl's `use` can have for example) to be wary of.
Thilo
2010-09-30 08:04:41
Thanks Thilo and Michael for the response.
Krishnan
2010-09-30 08:09:19
+1
A:
#import is a variant (that checks for duplication) of #include, which just results in the contents of the included file being pasted in your source file.
Java's import statement tells the compiler where to look for classes (and other things) that are not qualified by their full name in the source code.
Thilo
2010-09-30 07:52:58