Prev: call jni function dynamically without getting a JNIEnv handleas an argument.
Next: Telnetting to diff IP with same port number
From: Arne Vajhøj on 2 May 2010 21:29 On 02-05-2010 21:22, BGB / cr88192 wrote: > "Arne Vajh�j"<arne(a)vajhoej.dk> wrote in message > news:4bdcca13$0$279$14726298(a)news.sunsite.dk... >> On 30-04-2010 05:49, Arved Sandstrom wrote: >>> A lot depends on exactly what it is that people are writing. If I was >>> writing a Linux device driver in C I'd be cool with vim. But these days, >>> where I have to deal with .NET or J2EE web apps with thousands of source >>> files, I'd be an imbecile to try and do that with emacs. >> >> Emacs is pretty close to an IDE. >> >> But I don't know how good its Java and C# support is though. > > personally, IMHO, I find that Emacs is just horrid and prefer to stay well > clear of it... I am not particular happy with Emacs either. But just because it does not match my personal taste does not mean that it is not a good IDE. Arne
From: Arne Vajhøj on 2 May 2010 21:53 On 02-05-2010 07:05, Tom Anderson wrote: > I used Windows for years, during the '95 and 2000 eras. From a > programming perspective, it was an improvement on the MacOS 9 which i'd > been using before that. But OS X and Linux are a *huge* improvement on > Windows. That's my experience. Does that count as religious fanaticism? If you do not realize that it is your personal preference and that the majority of developers seems to think otherwise then YES. Arne
From: BGB / cr88192 on 2 May 2010 21:54 "Lew" <noone(a)lewscanon.com> wrote in message news:hrl3do$nse$1(a)news.albasani.net... > BGB / cr88192 wrote: >> but, granted: >> the majority of developers develop on Windows; >> the majority of those developers, in turn, either use MS tools (MSVC or >> MS >> Visual Studio), and very often, an MS technology (such as C# or VB.NET, >> or >> they may use J# as their preferred Java implementation). > > I strongly suspect that hardly anyone is using J#. > <http://msdn.microsoft.com/en-us/vjsharp/default.aspx> >> January 10, 2007: ... >> Since customers have told us that the existing J# feature set largely >> meets >> their needs and usage of J# is declining, Microsoft is retiring the >> Visual J# >> product and Java Language Conversion Assistant tool to better allocate >> resources for other customer requirements. The J# language and JLCA tool >> will >> not be available in future versions of Visual Studio. > fair enough... I don't personally use J# either, FWIW, but had thought probably some did, oh well... (checking, yeah, it seems the version of Visual Studio I have installed doesn't support it either, oddly I hadn't really noticed...). I mostly used Visual Studio for C#, and mostly text-editors and the shell for C and C++, and Eclipse for Java (although, I also use plain text-editors as well...). I tried using Eclipse for C/C++, but found this somewhat disappointing (more so, since I couldn't tell it to use MS's compiler as a backend, or figure out how to configure much of anything else related to building). > -- > Lew
From: Arne Vajhøj on 2 May 2010 21:55 On 02-05-2010 19:28, BGB / cr88192 wrote: > the majority of those developers, in turn, either use MS tools (MSVC or MS > Visual Studio), and very often, an MS technology (such as C# or VB.NET, or > they may use J# as their preferred Java implementation). Practically no one has used J#. After all a Java 1.1 source code compatible language is not that cool a decade after the Java world moved on. Arne
From: Arne Vajhøj on 2 May 2010 21:56
On 02-05-2010 16:11, Lew wrote: > On 05/02/2010 03:18 PM, Eric Sosman wrote: >> On 5/2/2010 2:27 PM, Lew wrote: >>> Arved Sandstrom wrote: >>>> Fortunately "may not" is one of the modal negatives that has a fairly >>>> unambiguous meaning, as in, "not allowed". That doesn't mean that a lot >>>> of people don't use it incorrectly, though. >>> >>> "Correctly" according to you. I've heard "may not" to mean "might not" >>> my entire life. >> >> "Mom, can I use the car?" >> >> "You mean `may'." >> >> "Sorry. Mom, may I use the car?" >> >> "No, you may not." > > Your point may not have been clear here. What are you trying to say? That "may not" can have a meaning as "absolutely not". Arne |