With every release of Windows, Microsoft scraps the old APIs and introduces new ones. The new ones don't solve many problems but are gratuitously incompatible with everything else.
IDIOT. That's all I can really say. You're so ignorant it's depressing.
And "Visual J++" was Microsoft's solution to Java. "Get all the benefits of Java with all the power of Windows", they said. Anyone who bought into that and staked their future on WFC and all that Windows-only Java are now going to find themselves at the unemployment office.
Visual J++ is the only reason why I supported the Java LANGUAGE.
If I had to, I would pay upwards of $2000 for visual studio, and most likely more cause it's more than worth it.
The official Microsoft stand point on easter eggs is that it shouldn't happen.
Easter eggs tend to be put in by engineers in the weekends and on their spare time (so they say).
I think cause of he relaxed attitude at Microsoft, noone really minds about the easter eggs, most probably think it's fun. But officially they have to say they don't support it (ofcourse).
Oh please. I remember that mars.exe program that was only a few K. It would have taken less than 100K to do that small flight simulator. Less than even one clipart that comes with office. The code for that sort of thing won't be that large....what makes things like flighsimulator 2000 big is the data for all the cities etc. Randomly generating a little terrain you fly around is not bloat, far from it.
The explorer shell is only one shell...and designed for use in PalmPC and HandHeldPCs. I think it's fine - but not particularly great on Palm-sized PCs, but there's NOTHING to stop you replacing the shell with your own "more appropriate" shell. Infact, I think CASIO ship a nice one with the E105.
I don't like the Palm default myself, and I usually install applauncher.
BTW WinCE devices can run the Palm Emulator fine too.
We just need to start shipping supplies to mars now, oxygen, buildings, food and water. And ofcourse cool things that'll make feuls out of the martion enviroment.
in a few decades we should have enuff supplies to make quite a nice colony on mars.
Office is more than just a suite of business tools now days, it's also a development tool, there's a hell of a lot of office developers out there now, whether it's writing Access databases or word/outlook plugins.
MS fund the open source projects ActiveState's Perl and Transvirtual's Kaffe...just to mention 2.
Redhat are still buying out companies, and it's to gain them in the end, just like MS does, so don't tell me that just cause they make it open source makes it all better. In the end, what could happen? Redhat corner the market in those areas, other projects like mozilla can't succeed. Who cares right? Mozilla is open source. Everyone who keeps complaning about MS should care, cause it's a marketing thing, noone will use anything but REDHAT supported mozilla.
2.) There's the famous Bill Gates "640k should be enough for anybody." quote from '81
that is becoming tiresome. Bill Gates did not mean enough for anybody for the entire future. He meant then and there. Just like if i were to tell someone who wanted to buy a PC today, 64MB will be enough for you. Bill Gates if anything, has always had vision, he's a technologist and a geek, don't play him for a fool.
ROFL that's one of the funniest things I've read today. Why did you introduce crap about compilers? Did I give you the slightest impression anywhere that compilers are fussy about naming conventions? All keywords should be lower case....how does that make _ME_ wrong? instanceOf is a method call because Java doesn't reserve it as a keyword; similarly, instanceof isn't a method call because Java *does* reserve it.
That is also another funny thing I've read today. instanceOf is that way cause of the method naming sceheme. What would the fact that instanceof is reserved have anything to do with it. Are you implying that I can't have a method called instanceof cause it's a keyword? ROFLMAO. My original post said that all those naming conventions are correct.
And using "is" is not strictly neeed. Since the operator has already been named instanceof, the method is naturally instanceOf (you can't depreciate keywords).
It's completely intuitive to me, and like I said in my original post, ALL of what was mentioned is consistant with the java naming conventions.
True (i do remember some highschool biology:)) But that's not unlike what computer circuits do with compiled binaries. The thing is compiled binaries don't normally still contain comments.
So after i've helped myself, where does his help come into it? The only need to add "him" to the equation would be to just satisfy preexisting religious ideas.
Um, I take it you don't know much about java. instanceof is a keyword, it's also an operator. instanceOf would be the name of a method call (i believe isInstance is a method in the Class class...it's the dynamic equivalent of instanceof). The conventions are fine, and *mostly* consistant.
The reason it's not a method is the same reason why = ^ | > etc aren't methods. What sun should have done is made == an overloaded operator for the String class like they did with +...but i'll save that argument for another time.
Willing yourself to be better is nothing to do with god or praying. People who feel down or depressed are more likley to be sick. Like people say laughter is the best medicine. The way people choose to make themselves feel better is individual, but the results are the same. I could sit here and pray to Papa Smurf and convince myself that it's make me feel better, and it prolly will.
Many people believe in god, and the belief is probably more important than the truth (with respect to this subject).
Ignore the conventions in Java for where to use upper case in variable and class names i.e. Classes start with upper case, variables with lower case, constants are all upper case, with internal words capitalised. After all, Sun does (e.g. instanceof vs isInstanceOf, Hashtable). Not to worry, the compiler won't even issue a warning to give you away. If your boss forces you to use the conventions, when there is any doubt about whether an internal word should be capitalised, avoid capitalising or make a random choice, e.g. use both inputFileName and outputfilename. You can of course drive your team members insane by inventing your own insanely complex naming conventions then berate others for not following them. The ultimate technique is to create as many variable names as possible that differ subtlely from each other only in case.
(e.g. instanceof vs isInstanceOf, Hashtable)
they are all valid w.r.t the conventions.
instanceof is an operator and a keyword hence should be all lowercase, isInstanceOf is a method name, hence should start with a lower case character and the rest of the words should be capatilized, and Hashtable is a class name hence every word should start with a capital. Hashtable is the only one you could argue, but I'd say that sun just think Hashtable is one compounded word in itself not two words that describe a class's function.
Slashdot Mirror
1.1.4.
Anyway, then that has nothing to do with "compiling Pure Java", but just to do with compiling Java 2 - which many IDEs don't fully support yet anyway.
I think you may have been sniffing too many of those sun "pure java" documents.
With every release of Windows, Microsoft scraps the old APIs and introduces new ones. The new ones don't solve many problems but are gratuitously incompatible with everything else.
IDIOT. That's all I can really say. You're so ignorant it's depressing.
And "Visual J++" was Microsoft's solution to Java. "Get all the benefits of Java with all the power of Windows", they said. Anyone who bought into that and staked their future on WFC and all that Windows-only Java are now going to find themselves at the unemployment office.
Visual J++ is the only reason why I supported the Java LANGUAGE.
If I had to, I would pay upwards of $2000 for visual studio, and most likely more cause it's more than worth it.
Um, you can compile pure java in J++ anyway.
J++ isn't something that runs around compiling to non java 1.1 compliant bytecode. There are extensions - just don't use them.
And yes, MS make very good extensible IDEs.
Visual J++ is already a decent product. It's the best editor and compiler out there for Java 1.1
Where the hell did you get that from?
It does a scrolling box with the credits.
The official Microsoft stand point on easter eggs is that it shouldn't happen.
Easter eggs tend to be put in by engineers in the weekends and on their spare time (so they say).
I think cause of he relaxed attitude at Microsoft, noone really minds about the easter eggs, most probably think it's fun. But officially they have to say they don't support it (ofcourse).
Oh please. I remember that mars.exe program that was only a few K. It would have taken less than 100K to do that small flight simulator. Less than even one clipart that comes with office.
The code for that sort of thing won't be that large....what makes things like flighsimulator 2000 big is the data for all the cities etc. Randomly generating a little terrain you fly around is not bloat, far from it.
The explorer shell is only one shell ...and designed for use in PalmPC and HandHeldPCs. I think it's fine - but not particularly great on Palm-sized PCs, but there's NOTHING to stop you replacing the shell with your own "more appropriate" shell.
Infact, I think CASIO ship a nice one with the E105.
I don't like the Palm default myself, and I usually install applauncher.
BTW WinCE devices can run the Palm Emulator fine too.
We just need to start shipping supplies to mars now, oxygen, buildings, food and water. And ofcourse cool things that'll make feuls out of the martion enviroment.
in a few decades we should have enuff supplies to make quite a nice colony on mars.
Oh Please.
It's not based on Win31. It's based on NT.
It's a preemptive, multithreaded multasking OS with a microkernel.
It has capabilities that PlamOS couldn't hope to reach any time soon.
OpenGL is just a graphics library (on windows it runs ontop of DirectX).
DirectX was designed to allow windows applications to directly access video memory, it also has sound, and networking apis.
And what the hell do you want? A double sided wand?
I guess you don't like your Macs either?
Uh I think it was meant to be funny.
Office is more than just a suite of business tools now days, it's also a development tool, there's a hell of a lot of office developers out there now, whether it's writing Access databases or word/outlook plugins.
Uh huh.
MS fund the open source projects ActiveState's Perl and Transvirtual's Kaffe...just to mention 2.
Redhat are still buying out companies, and it's to gain them in the end, just like MS does, so don't tell me that just cause they make it open source makes it all better. In the end, what could happen? Redhat corner the market in those areas, other projects like mozilla can't succeed. Who cares right? Mozilla is open source. Everyone who keeps complaning about MS should care, cause it's a marketing thing, noone will use anything but REDHAT supported mozilla.
2.) There's the famous Bill Gates "640k should be enough for anybody." quote from '81
that is becoming tiresome. Bill Gates did not mean enough for anybody for the entire future. He meant then and there. Just like if i were to tell someone who wanted to buy a PC today, 64MB will be enough for you.
Bill Gates if anything, has always had vision, he's a technologist and a geek, don't play him for a fool.
ROFL that's one of the funniest things I've read today. Why did you introduce crap about compilers? Did I give you the slightest impression anywhere that compilers are fussy about naming conventions?
All keywords should be lower case....how does that make _ME_ wrong?
instanceOf is a method call because Java doesn't reserve it as a keyword; similarly, instanceof isn't a method call because Java *does* reserve it.
That is also another funny thing I've read today.
instanceOf is that way cause of the method naming sceheme. What would the fact that instanceof is reserved have anything to do with it. Are you implying that I can't have a method called instanceof cause it's a keyword? ROFLMAO.
My original post said that all those naming conventions are correct.
And using "is" is not strictly neeed. Since the operator has already been named instanceof, the method is naturally instanceOf (you can't depreciate keywords).
It's completely intuitive to me, and like I said in my original post, ALL of what was mentioned is consistant with the java naming conventions.
True (i do remember some highschool biology :))
But that's not unlike what computer circuits do with compiled binaries.
The thing is compiled binaries don't normally still contain comments.
I guess either
1) God doesn't have a very good DNA compiler
or
2) God decided to make DNA an interpreted language!
So after i've helped myself, where does his help come into it?
The only need to add "him" to the equation would be to just satisfy preexisting religious ideas.
Um, I take it you don't know much about java.
...but i'll save that argument for another time.
instanceof is a keyword, it's also an operator.
instanceOf would be the name of a method call (i believe isInstance is a method in the Class class...it's the dynamic equivalent of instanceof).
The conventions are fine, and *mostly* consistant.
The reason it's not a method is the same reason why = ^ | > etc aren't methods.
What sun should have done is made == an overloaded operator for the String class like they did with +
Willing yourself to be better is nothing to do with god or praying.
People who feel down or depressed are more likley to be sick. Like people say laughter is the best medicine. The way people choose to make themselves feel better is individual, but the results are the same. I could sit here and pray to Papa Smurf and convince myself that it's make me feel better, and it prolly will.
Many people believe in god, and the belief is probably more important than the truth (with respect to this subject).
Ignore the conventions in Java for where to use upper case in variable and class names i.e. Classes start with upper case, variables with lower case, constants are all upper case, with internal words capitalised. After all, Sun does (e.g. instanceof vs isInstanceOf, Hashtable). Not to worry, the compiler won't even issue a warning to give you away. If your boss forces you to use the conventions, when there is any doubt about whether an internal word should be capitalised, avoid capitalising or make a random choice, e.g. use both inputFileName and outputfilename. You can of course drive your team members insane by inventing your own insanely complex naming conventions then berate others for not following them. The ultimate technique is to create as many variable names as possible that differ subtlely from each other only in case.
(e.g. instanceof vs isInstanceOf, Hashtable)
they are all valid w.r.t the conventions.
instanceof is an operator and a keyword hence should be all lowercase, isInstanceOf is a method name, hence should start with a lower case character and the rest of the words should be capatilized, and Hashtable is a class name hence every word should start with a capital. Hashtable is the only one you could argue, but I'd say that sun just think Hashtable is one compounded word in itself not two words that describe a class's function.
:P
TROLL