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 20:38:26 +0000 (UTC) Organization: UK Free Software Network Lines: 21 Message-ID: References: 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 1347482306 30210 84.45.235.129 (12 Sep 2012 20:38:26 GMT) X-Complaints-To: usenet@localhost.localdomain NNTP-Posting-Date: Wed, 12 Sep 2012 20:38:26 +0000 (UTC) User-Agent: Pan/0.139 (Sexual Chocolate; GIT bf56508 git://git.gnome.org/pan2) Xref: csiph.com comp.lang.java.programmer:18695 On Wed, 12 Sep 2012 13:21:25 -0700, 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/C++ #include statements can, and often do, contain further nested #includes, so its quite possible that not all of these will be inside the #ifndef ... #endif brackets that should check for and skip multiple inclusions. Since, unlike a C/C++ #include statement, an import doesn't pull in any source code, Java can never have this sort of clash. -- martin@ | Martin Gregorie gregorie. | Essex, UK org |