Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail From: Lew Newsgroups: comp.lang.java.programmer Subject: Re: How to develop without an IDE? Date: Wed, 2 May 2012 14:20:43 -0700 (PDT) Organization: http://groups.google.com Lines: 102 Message-ID: <17845189.2140.1335993643566.JavaMail.geo-discussion-forums@pbnh4> References: <4f94338d$0$295$14726298@news.sunsite.dk> <4f94765c$0$284$14726298@news.sunsite.dk> <4f949830$0$295$14726298@news.sunsite.dk> <4f9cb523$0$293$14726298@news.sunsite.dk> <4f9d8965$0$288$14726298@news.sunsite.dk> <4f9f446b$0$288$14726298@news.sunsite.dk> <5183845.788.1335981689730.JavaMail.geo-discussion-forums@pbbof7> NNTP-Posting-Host: 69.28.149.29 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1335993970 3222 127.0.0.1 (2 May 2012 21:26:10 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Wed, 2 May 2012 21:26:10 +0000 (UTC) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=69.28.149.29; posting-account=CP-lKQoAAAAGtB5diOuGlDQk0jIwmH0T User-Agent: G2/1.0 X-Received-Bytes: 5389 Xref: csiph.com comp.lang.java.programmer:14153 On Wednesday, May 2, 2012 12:21:25 PM UTC-7, BGB wrote: > On 5/2/2012 11:01 AM, Lew wrote: > > BGB wrote: > >> Arne Vajh=F8j wrote: > >>> BGB wrote: > >>>> Arne Vajh=F8j wrote: > >>>>> Java import and C include is not similar at any distance. > >>>>> > >>>> > >>>> well, both are used to make use of a library, > >>> > >>> Neither of them are used to make use of a library. > >>> > >>> Java import allows you to reference classes without package name. > >>> > >>> C include includes some source code from another file in the > >>> compilation of current file. > >>> > >> > >> this is what they do (or, how they work), but the issue is not what th= ey > >> do, but what purpose they are used for. > >> > >> > >>>> both also have a word starting with the same letter and appear near = the > >>>> top of a source file, and are vaguely similar looking, also sort of > >>>> making them "similar". > > > > Clearly you are joking here. > > > >>> C include can be anywhere in the file. > >> > >> but is most often at the top (except maybe when writing headers or > >> similar, where near the bottom is also common). > > > > "Most often" is stylistic; the discussion here is how the constructs ar= e dissimilar, and Java 'import' must be at the top, just as Arne said, and = that is a difference. Your so-called counterargument is irrelevant as it do= es not countervail the difference. > > > >>> They do both start with "i", but so does ice cream. > >> > >> yes, but ice-cream is not a keyword in either language. > > > > And "include" is not a keyword in Java. The comparison is both inaccur= ate and blazingly irrelevant. I know you are just jerking us around, but it= 's causing people to answer you seriously, BGB, so please stop. > > >=20 > I was not joking here... Oh, my goodness. I am shocked. > this was mostly a matter of "how pedantic or technically accurate a=20 > statement should be". Your statements went far past pedantry deep into the territory of utter use= lessness. The similarity that you propose of both beginning with the letter "i", for = example, is so stupid as to be insulting, unless meant as a joke. It's also= wrong, since the C directive begins with "#", not "i". Try to stay with the program here. People are having a serious discussion. > in this case, a technically inaccurate statement was used to make a=20 > point, but the technical inaccuracy would be "excusable" under the basis= =20 > that many people wouldn't really care that they are different in these=20 > regards, seeing them as "similar". It was not excusable, not even with quotation marks. C's '#include" and Jav= a's "import" are far too dissimilar to allow anyone to muddle them. This is= a computer programming forum, and accuracy in this area is not mere pedant= ry. You say "technically inaccurate" as if that somehow is different from "wron= g". > so, the assertion is that strict technical accuracy is not always=20 > necessary, or for that matter, beneficial. That has nothing to do with the topic of the similarities and differences b= etween C's '#include' and Java's 'import'. Here, not being wrong is both ne= cessary and beneficial. > do people make a big fuss over "the sun rises and the sun sets" when=20 > in-fact it is the Earth that is moving? WTF does that have to do with the price of tea in Beijing? > in this case, the distinction is itself largely irrelevant. What distinction? Are you saying the distinction between C's '#include' and= Java's 'import' is irrelevant to this discussion, because it's not. Wrong ideas about programming are not beneficial to programmers, and "techn= ically inaccurate" is wrong. --=20 Lew