Fairly uninteresting topic, just asking for what Java compilers you guys use.

Last year we did a course of Java and we used this lovely little program called PhysEdit, but it seems it was developed by someone at our University and I can't download it anywhere. I'd like to brush up on my Java skillz before our further programming course next year, so what compilers or programs do you guys use?

Eclipse.

Yep, Eclipse is the best one i've seen.

Do you mean IDEs? Eclipse is the best free one. A lot of people say IntelliJ IDEA is better, but it's not free.

Just incase it hasn't been mentioned enough, eclipse.

Eclipse

I personally use a Mr. Coffee to compile my Java.

Vim and javac doesn't work... why?

He must be talking about IDEs.

Notepad here, personally.

If I feel like using a sledgehammer to hang a picture frame, I use Eclipse.

Well, VIM at least has color coding, which is really useful.

I disagree. I've used color-coding extensively and I think going without is a little bit easier (for me, anyway). It's a lot less cluttered; easier to focus on what's important in my opinion.

Also, color-coding is hardly VIM's premeire feature.

Because vim is not an IDE and is about as useful for large projects as a rock hammer is for digging a subway tunnel.

You're weird, Free. Color coding cancels clutter, you crazy cook.

Notepad++

If you just want to write code, Textpad has syntax highliting and can tie into the default java compiler.

I just look at it this way: the only purpose of color-coding is to help distinguish between types of tokens: identifiers, keywords, operators, etc. Yet, those things are already distinguished quite thoroughly by the very symbol. The only conceivable problem area is distinguishing between keywords and identifiers, but really, if you've been programming for more than a week and have trouble with that, there is no hope for you.

Color-coding, therefore, adds an additional layer of complexity to code and hardly any benefits. A color-coded token does not take any less time for me to decipher than a non-color coded one. Not appreciably, anyway.

Edit: nice alliteration, by the way.

Ok teapot.

For my school assignments I mainly used nedit/gedit or Notepad++ depending on which OS I was using. For larger projects I used Eclipse.

I'm going to go with the "you don't have much experience in programming".

"Syntax Highlighting" is a very nice feature to have. Especially when you have tons of quote marks, strings, brackets, and other random crap all next to eachother. It makes it VASTLY easier to scan a document for what you're looking for, as well as easily showing typos and other mistakes.

So yeah, I think you're looney.

notepad++ if it's just something lightweight. If it's a large project or requires a debugger(makes life 100x easier) at all then Eclipse is a must.

If that makes you feel like a bigger man, then I'm happy for you. Go for it.

sh, ls, mkdir, cat, echo, ed, grep, sed, awk, sam, acme

I was being serious. I don't see how any seasoned/experienced programmer could possibly make that statement, save maybe people who grew up using punch cards and enjoy masochism.

I was being serious too.

I'm inclined to agree with Free on this one. The only time I've found color-coding helpful is if I'm not sure the name of a library function and finding typos, both of which are uncommon. I have a good enough memory that I can remember what everything is and means without colors, and bad enough ADD that I get distracted wondering when my letters are going to change color as I type them and if I could have programmed the IDE's token recognition better

It's not about remembering what something does. It's about being able to see it in a massive block of crap. >.>

Whatever.

Let me just clarify: I'm only talking about syntax highlighting. I'm not talking about real-time compile error/typo finders ala Eclipse. Those things are geniunely useful, but outside the scope of syntax highlighting.

glunix is garbage

syntax coloring is virtually pointless for writing or debugging code, and it doesnt even help that much with just scanning over large blocks of code.

much more useful in all three of those situations is just to structure the code to use a consistent format.


take your pick

----------------------------------------------------------------------

class watever: public som{ protected : virtual int Blah() const ; public :watever& operator =( const watever& o);};

------------------------------- OR ----------------------------------

class CWhatever : public ISomething
{
protected:
virtual int Blah() const;

public:
CWhatever &operator=(const CWhatever &o);
};

----------------------------------------------------------------------



what IS handy as hell that notepad wont provide is

-context sensitive vars/methods/param display (a la Intellisense, when it works)
-automated indentation
-highlighting matching open/close parens and brackets


syntax coloring is one of those things thats like its easy as hell to implement in an ide so hey.. why not?

You can combine the two. That's why it's useful. If you're going to attempt to make an argument, don't pick the worst case of the one you don't like.



But VIM will, and it's not as bloated as an IDE.

This is why I disagree:

[php]
elseif($_POST['type'] == 'ACC') { // They provided an account number, so we skip a few steps looking it up
$loginresult = mysql_query("SELECT * FROM `login` WHERE `userid` LIKE '". $searchfield ."'");
if (mysql_num_rows($loginresult) != 1) {
die("Account name doesn't exist");
}
$account = mysql_fetch_assoc($loginresult);
$deepsearchresult = mysql_evaluate_array("SELECT `name` FROM `char` WHERE `account_id` ={$account['account_id']} AND `name` NOT LIKE '{$searchfield}'");
foreach($deepsearchresult as $deepsearchfield) {
$gmbanresult = mysql_fetch_assoc(mysql_query("SELECT * FROM `gmban` WHERE `reason` LIKE '%". mysql_real_escape_string($deepsearchfield) ."' ORDER BY `time` DESC LIMIT 0, 1"));
if($gmbanresult) {
if($gmbanresult['type'] > 0) {
$reason = explode("* ", $gmbanresult['reason'], 2);
echo "<p>The account <strong>{$searchfield}</strong> was banned on the character <strong>{$deepsearchfield}</strong>, at <strong>{$gmbanresult['time']}</strong> by <strong>{$gmbanresult['gm_char_name']}</strong> because <strong>\"{$reason[0]}\"</strong>. </p>";
$foundban = TRUE;
break;
}
}
}
if (!$foundban) { // If the ban wasn't found there's only two reasons why
$state = mysql_result(mysql_query("SELECT `state` FROM `login` WHERE `account_id` ={$account['account_id']}"), 0);
if($state == 0) {
echo "<p>User {$searchfield} is not banned!</p>";
}
else {
echo "<p>User was banned by the server. (See admin for details)</p>";
}
}
}

[/php]Edit: Double Edit: Triple Edit: There now the code is displaying properly >.>

Looks a helluva lot easier to read to me than a sheet of text like this:

terrible thread

My last compile: javac

I usually use Eclipse for stuff, though.

I want to learn vim. I feel insignificant using nano.

I use Crimson Editor for Java unless i'm doing something more than a couple of classes then I'll use eclipse, but usually I won't use java for such a program anyway

oh and how can people not like Syntax highlighting? I find it useful, I can quickly skim a piece of code and get an idea of what it does by just reading function names because they're in a specific colour.

More important that syntax highlighting is bracket matching. I couldn't code without that.

The one thing I really miss when it's not there is regex find/replace. I didn't realise how much I used it until I had to use an editor without it

why in god's name did you start with nano? Idiotic glunix establishment. Start with ed and move to sam

I think you're just making up acronyms now.

what?

Separating a contiguous block of information with different colors or shapes always makes it easier to process for your mind. Unless maybe your brain is broken.

'color coding' undermines the unit character byte and cannot be parsed by regular expressions, and it emphasizes course grain units depicted by colors, regardless of any sub-units a single color may encompass. And it's plain ugly, annoying, and bearing no self description of color semantics it destroys portability. Rob pike doesn't like it, so neither do i. Text is god, and he is jesus

CM, have you ever heard of the 80x40 rule? One of the veteran programmers I knew a while ago taught it to me. Basically it states that every function/method you write should fit, in its entirety, on a Text Mode Terminal (80 Columns by 40 Lines ballpark). If you have a function that doesn’t fit, refractor until it does.

It’s a hard rule to live by, but it really does force you to write better, cleaner, and leaner code. There are some exceptions (like writing interface code), but I try to keep to it as often as possible.

As for Syntax Highlighting, it can be exceptionally useful. not in writing code, but as has been pointed out in quickly recognizing where you are in your code, and giving your visual landmarks to help navigate by. Try becoming intimately familiar with 10,000 lines of code… Syntax Highlighting is just another tool to help you learn where you are and what your doing. Of course it’s not essential, but then again, you could always just echo you terminal into a file directly… If you wanted.