Byte code is interpreted by an interpreter. machine code is processed by the CPU. basic is interpreted which run slow by reading text and translating. but if you transform it into byte code{function numbers} it will run faster by calling Function[number] in the function table instead of looking up a text command in a command list. java use to be interpreted but now you compile it into byte code to be interpreted faster. I think they also code the variables in a variable table as well as the functions, so there's no text to translate plus it make them smaller. Variable 100 {variabletable[100]} is quicker and smaller than looking up myvariablename each byte code tells whether it a command or a variable and how many arguments
brianhood
Posts
-
Machine code and byte encoders -
java and .netyour right I think it was javascritp they had a fite about.
-
java and .netBig response, but what about WordPerfect, being crushed by MS free words. IBM approached Digital Research to produce an operating system. sounds like this was a contract,and seems like IBM would have gained ownership,like when you buy something. must have been a bad contract, and software is not like tangible goods. MS agreed to create an operating system and went out and bought one I use nothing but MS as my OS, I just feel for the little guy, and hate to see anybodt get bullied.
-
java and .net.net is just a MS. Version/rewrite of Java from when Sun and Ms. had a falling out about Names and Procedures, and when Sun Sued Ms. Ms. got mad and wrote there on, as not to be bound by Java and to crush it. as with all MS ideas it borrowed used or stolen. starting from it OS on. if you do not know Bill created his OS when he worked for IBM(i.e.. DOS), but had a Right to use the works. as the courts ruled.
-
another preference question....exactly: and in easier terms. constructor and the destructor or for memory management. init() is for class that have to many properties to pass in as arguments. unless you won't to use a config file/mem and decipher. ounces the object is constructed ,even if all it does is initialize the object to a NULL state, then you can set properties and call Init() ,the destructor in where you clean up,even if you got to call special function from the destructor, to keep the code clean.
-
another preference question....constructor and the destructor or for memory management. init() is for class that have to many properties to pass in as arguments. unless you won't to use a config file/mem and decipher. ounces the object is constructed ,even if all it does is initialize the object to a NULL state, then you can set properties and call Init() the time the destructor in where you clean up,even if you got to call special function from the destructor, to keep the good clean.