Not many can claim 25 years on the Internet! Join us in celebrating this milestone. Learn more about our history, and thank you for being a part of our community!
class Main
{
public static int main (blarhg)
{
System.out.println ("Hello World");
}
}
import System; //some static class exported by the app in which
//janko is embedded
object SomeOtherJankoObject
{
object PrintText (string text)
{
System.print (text);
}
}
import SomeOtherJankoObject
SomeOtherJankoObject obj;
obj.PrintText("Hi Beyotch!");
class Main{ public static int main (blarhg) { System.out.println ("Hello World"); }}print "Hello World"function main() print "Hello World"endMain ={ main = function () print "Hello World" end}Quote: Original post by Matei
Well, I'd say that print "Hello World" is understandable to anyone who knows English, whereas System.out.println is pretty cryptic.
However, I'm really wondering why you're making no distinction between functions and objects. I think this makes the language more confusing, and is also wrong at a conceptual level. A function is a representation of an algorithm. An object is data, with perhaps some functions that operate on that data. It doesn't make sense for a function to have "fields" or "properties" like an object does. Nor does it make sense for an object to be "executed", or to take "arguments" (well, unless it's an object representing a function).
exposed inheritable int State;block block_that_returns_a_custom_block returns lambda{ ... return lambda { ... stuff that is returned. }}//or return another named block blockblock other_block (int arg) returns block_that_returns_a_custom_block{ ...}function scriptStart printout "Hello World";endobject badGuy health; //typeless name; function setName name = setName(1); //simple argument lookup end function onCollision health = health - 10; endend
