Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!usenet.ukfsn.org!not-for-mail From: Martin Gregorie Newsgroups: comp.lang.java.programmer Subject: Re: import order Date: Wed, 12 Sep 2012 21:53:51 +0000 (UTC) Organization: UK Free Software Network Lines: 27 Message-ID: References: <3a82498e-61e5-4438-b665-3d60b170dce0@googlegroups.com> NNTP-Posting-Host: 84.45.235.129 Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: localhost.localdomain 1347486831 31511 84.45.235.129 (12 Sep 2012 21:53:51 GMT) X-Complaints-To: usenet@localhost.localdomain NNTP-Posting-Date: Wed, 12 Sep 2012 21:53:51 +0000 (UTC) User-Agent: Pan/0.139 (Sexual Chocolate; GIT bf56508 git://git.gnome.org/pan2) Xref: csiph.com comp.lang.java.programmer:18703 On Wed, 12 Sep 2012 14:31:59 -0700, Lew wrote: > Robert Klemme wrote: >> bob smith wrote: >>> Does order ever matter with import statements in Java? >> >>> I don't think so. >>> I noticed it does sometimes matter with C++. Why the difference? > >> C++ does not have import statements - as simple as that. > > But it does have an '#import' directive, at least in the MS world. > http://msdn.microsoft.com/en-us/library/8etzzkb6(v=vs.71).aspx > Thanks for the link: I've never used MS C/C++ compilers, so #import was news to me. That said, it appears that #import pulls in and/or generates some sort of proprietary type definition file plus an #include file. So, it would appear that #import would suffer from exactly the same ordering problems as #include does. -- martin@ | Martin Gregorie gregorie. | Essex, UK org |