Get mp3 Michael Buble Pitbull MP3 search Gipsy Kings Nat King Cole All mp3 genres Coil Neil Young Suzy Solar Shakira Eva Cassidy Stevie Ray Vaughan Cobra Starship Comments on: Java-like Object-Oriented Code in Javascript http://www.uselesspickles.com/blog/2006/06/02/java-like-object-oriented-code-in-javascript/ ...or is it Use Less Pickles? Thu, 29 Jul 2010 12:58:05 +0000 http://wordpress.org/?v=2.0.1 by: I am just a programmer » Java-like Object-Oriented Code in Javascript http://www.uselesspickles.com/blog/2006/06/02/java-like-object-oriented-code-in-javascript/#comment-1549 Mon, 05 Nov 2007 14:58:22 +0000 http://www.uselesspickles.com/blog/2006/06/02/java-like-object-oriented-code-in-javascript/#comment-1549 [...] read more | digg story [...] […] read more | digg story […]

]]> by: UselessPickles http://www.uselesspickles.com/blog/2006/06/02/java-like-object-oriented-code-in-javascript/#comment-6 Sun, 04 Jun 2006 05:25:18 +0000 http://www.uselesspickles.com/blog/2006/06/02/java-like-object-oriented-code-in-javascript/#comment-6 Thanks, Ben. Every couple of cents helps :). I actually did have abstract implemented like that at one point. If you tried to instantiate an abstract class, an exception would be thrown with a message that listed the abstract methods and in which class they were declared. I ended up removing that constructor-time check to reduce overhead. I think I will put the constructor-time check back in with new plans of eventually having 2 versions of the library: a development version with all the error-detection that will make development easier, and a stripped down production version with minimal error detection to reduce the file size and run-time overhead. Any thoughts on if/when it is appropriate for static properties to be inherited? I'm thinking it makes sense for interfaces to inherit statics from other interfaces that they extend, but I'm second-guessing my decision to have classes inherit statics from the interfaces they implement (but I think that's how Java works). If I continue to have classes inherit statics from interfaces, I should probably also make classes inherit statics when they extend a class. Thanks, Ben. Every couple of cents helps :) .

I actually did have abstract implemented like that at one point. If you tried to instantiate an abstract class, an exception would be thrown with a message that listed the abstract methods and in which class they were declared. I ended up removing that constructor-time check to reduce overhead. I think I will put the constructor-time check back in with new plans of eventually having 2 versions of the library: a development version with all the error-detection that will make development easier, and a stripped down production version with minimal error detection to reduce the file size and run-time overhead.

Any thoughts on if/when it is appropriate for static properties to be inherited? I’m thinking it makes sense for interfaces to inherit statics from other interfaces that they extend, but I’m second-guessing my decision to have classes inherit statics from the interfaces they implement (but I think that’s how Java works). If I continue to have classes inherit statics from interfaces, I should probably also make classes inherit statics when they extend a class.

]]> by: Ben Newman http://www.uselesspickles.com/blog/2006/06/02/java-like-object-oriented-code-in-javascript/#comment-5 Sun, 04 Jun 2006 04:28:34 +0000 http://www.uselesspickles.com/blog/2006/06/02/java-like-object-oriented-code-in-javascript/#comment-5 In order for the abstract method feature to be truly useful, I do think you need to check conformance at compile time (or the closest thing in javascript, class creation time). It shouldn't be hard to determine whether a class has abstract methods; just count them when the class is defined, and store the count. When you inherit from an abstract class, with each method you add, check to see whether the base method was abstract, and if the new method isn't abstract, decrement the count for the new class. Only classes with an abstract method count of zero can be instantiated. When inheriting from abstract classes, the programmer needs to find out as soon as possible if something's awry. It's nice to see someone demonstrating the full extent of what can be done with javascript. You definitely have the right approach -- make something useful, and then make it better. Good luck with it. I'll be happy to keep tossing in my few cents. Ben In order for the abstract method feature to be truly useful, I do think you need to check conformance at compile time (or the closest thing in javascript, class creation time). It shouldn’t be hard to determine whether a class has abstract methods; just count them when the class is defined, and store the count. When you inherit from an abstract class, with each method you add, check to see whether the base method was abstract, and if the new method isn’t abstract, decrement the count for the new class. Only classes with an abstract method count of zero can be instantiated. When inheriting from abstract classes, the programmer needs to find out as soon as possible if something’s awry.

It’s nice to see someone demonstrating the full extent of what can be done with javascript. You definitely have the right approach — make something useful, and then make it better. Good luck with it. I’ll be happy to keep tossing in my few cents.

Ben

]]>