In office I dread every time I do copy/paste since I know it will inevitability do the wrong thing. Please always paste in context. Do not paste with formatting.
I know I sound like an old fuddy duddy but you could host your own usenet server and provide a news:// link. Newsreaders IMO have a better user experience and you can keep the out spam.
That's why I hate retarded douche-bags who can't be bothered to read the context. The parent was talking about finding root causes of null pointers. I pointed out that if errors are properly logged the stack trace would include the "caused by". So why don't you do the world a favor and eat shit and die.
In Java since properties are explicit it's obvious for example that the following would be problematic.
for (int j = 0; j getCount(); j++) { }
I'm calling a method which is more expensive but worse the method's result is not deterministic. What if this method is a part of a web service or using a database call? Again, it's obvious when code-reviewing that this should be written like:
int count = getCount(); for (int j = 0; j count; j++) { }
Unfortunately C# would use:
for (int j = 0; j Count; j++) { }
which is less obvious.
In fact there's so much bad code like this in C# that they had introduce the strange "yield" keyword to help alleviate the issues caused by this feature.
Do you have an example of this? I rarely need to use the debugger in Java. I can usually spot the bug in a few minutes looking at the code. But I use IntelliJ not Eclipse.
AnyCPU != Universal Binary since all your DLL dependencies need to align with the target platform as well. Realistically you need to create a separate project for each target in your Solution. Java has a true universal single binary. Build a jar and drop it on 32 bit WinXP, 64 bit windows 7, Linux, Mac - double click on it and it runs. Big difference.
Not sure what you mean by streamlined approach. Our company just finished an 18 month push into 64 bit with.NET. Our Java products were ready right away. No fuss - no muss - single binary. Gotta love it.
Slashdot Mirror
With all the talk about WinRT, Android and IOS - worth noting....
and play for your software you fucken leech.
Very cool thanks! This was one of the nice features of the TI - that you could easily redefine character images.
In office I dread every time I do copy/paste since I know it will inevitability do the wrong thing. Please always paste in context. Do not paste with formatting.
http://www.md5crack.com/ uses google to find MD5 strings that have been indexed. No algorithm required.
Can it run on Virtualbox?
Just set it 1000 years later and have a new set of characters.
I know I sound like an old fuddy duddy but you could host your own usenet server and provide a news:// link. Newsreaders IMO have a better user experience and you can keep the out spam.
Really?
You're a fucken inbred retard. Go back to your cave you whiny crybaby.
That's why I hate retarded douche-bags who can't be bothered to read the context. The parent was talking about finding root causes of null pointers. I pointed out that if errors are properly logged the stack trace would include the "caused by". So why don't you do the world a favor and eat shit and die.
Yeah that's why we see this kind of code often in msdn examples.
Yeah returning null is usually an error. Devs should read Effective Java more often. ;) However you'd still get a stack trace with a "caused by".
In Java since properties are explicit it's obvious for example that the following would be problematic.
for (int j = 0; j getCount(); j++) {
}
I'm calling a method which is more expensive but worse the method's result is not deterministic. What if this method is a part of a web service or using a database call? Again, it's obvious when code-reviewing that this should be written like:
int count = getCount();
for (int j = 0; j count; j++) {
}
Unfortunately C# would use:
for (int j = 0; j Count; j++) {
}
which is less obvious.
In fact there's so much bad code like this in C# that they had introduce the strange "yield" keyword to help alleviate the issues caused by this feature.
Properties at the language level was a bad idea.
log.error(e.getMessage(), e) will give you the stack trace.
Do you have an example of this? I rarely need to use the debugger in Java. I can usually spot the bug in a few minutes looking at the code. But I use IntelliJ not Eclipse.
Except properties at the language level is a bad idea since it hides performance deficits and there's no good convention for it.
AnyCPU != Universal Binary since all your DLL dependencies need to align with the target platform as well. Realistically you need to create a separate project for each target in your Solution. Java has a true universal single binary. Build a jar and drop it on 32 bit WinXP, 64 bit windows 7, Linux, Mac - double click on it and it runs. Big difference.
Not quite. C# lacks a universal binary. You need to build for each platform which is a PITA compared to Java.
You're not sophisticated.
Not sure what you mean by streamlined approach. Our company just finished an 18 month push into 64 bit with .NET. Our Java products were ready right away. No fuss - no muss - single binary. Gotta love it.
America needs to support the Afghan (tm) economy of course. ;)
Mod parent up.
Mod up. Sheesh only on slashdot would a simple question require 50 pages of scrolling to find an answer....
You mean to say that in America you elect presidents who have no stated policy on these critical questions? Well that explains it....