Re: [OT] Re: import

[Jeff Teunissen]

Nicola Pero wrote:
> 
> Ok - I think my answer was nor very precise, but I've done my homeworks
> now.
> 
> > It does not matter.  This kind of problem is not handled by any
> > compiler/language. What if you defined two classes with the same name
> > in different files with different path? Whatever the language, you can
> > confuse the compiler with links to the same file.  Programming
> > languages/compilers don't impose any mapping between objects described
> > in the language and files (that would link the language to a given
> > file system!).  That's why it's usefull to have higher level
> > constructs in the language such as packages, modules, classes,
> > whatever.
> 
> #import in C/ObjC is *not* such a higher level construct.
> 
> #import in C/ObjC *is* defined in terms of files, so in term of the
> filesystem.

How so? #include isn't, so how is #import?

[snip]

-- 
| Jeff Teunissen  -=-  Pres., Dusk To Dawn Computing  -=-  deek @ d2dc.net
| GPG: 1024D/9840105A   7102 808A 7733 C2F3 097B  161B 9222 DAB8 9840 105A
| Core developer, The QuakeForge Project        http://www.quakeforge.net/
| Specializing in Debian GNU/Linux              http://www.d2dc.net/~deek/