From: Michael H. <mi...@hu...> - 2008-03-04 15:01:42
|
Hello, what is the difference between "Dynamic compilation to Java bytecodes" and the "static compilation" ? Thanks !! Michael |
From: David H. <dav...@gm...> - 2008-03-04 15:49:51
|
On Tue, Mar 4, 2008 at 9:01 AM, Michael Hüttermann <mi...@hu...> wrote: > Hello, > > what is the difference between "Dynamic compilation to Java bytecodes" and > the "static compilation" ? > > Thanks !! > > Michael Static compilation is done at compile-time, creating Java class files (.class files) that can be deployed and loaded like any other class files, by code that doesn't know anything about Jython. Dynamic compilation happens at runtime and must be initiated by code that calls the Jython library. Statically compiled files are much easier to work with, but Python is too dynamic to be fully statically compiled. - David |
From: Michael H. <mi...@hu...> - 2008-03-04 16:03:48
|
this means that Jython is either statically compiled *or* dynamically compiled *or* not compiled in the runtime environment? These are the three possibilities? Thanks !!! > Static compilation is done at compile-time, creating Java class files > (.class files) that can be deployed and loaded like any other class > files, by code that doesn't know anything about Jython. Dynamic > compilation happens at runtime and must be initiated by code that > calls the Jython library. Statically compiled files are much easier > to work with, but Python is too dynamic to be fully statically > compiled. > > - David > > |
From: A. P. ☀ <the...@gm...> - 2008-03-04 16:27:03
|
On Tue, Mar 4, 2008 at 6:03 PM, Michael Hüttermann <mi...@hu...> wrote: > this means that Jython is either statically compiled *or* dynamically > compiled *or* not compiled in the runtime environment? These are the three > possibilities? > > Thanks !!! > Basically you have interpreted vs compiled. Compilation can be further branched down to statically vs dynamically compiled. As David already said basically statical vs dynamical compilation is the same process but applied at different moment and with a small difference on the output (statical: there is a compilation step during the build process, it generally results in a specific output -- in the JVM case compilation leads to .class files; dynamic: there is not a separate compilation step involved during the build process, but rather this is done during the execution of the program, and the output (in the case of JVM) is still bytecode but not in the form a files, but rather bytecode that gets loaded into the VM). cheers, ./alex -- .w( the_mindstorm )p. > > > > > > Static compilation is done at compile-time, creating Java class files > > (.class files) that can be deployed and loaded like any other class > > files, by code that doesn't know anything about Jython. Dynamic > > compilation happens at runtime and must be initiated by code that > > calls the Jython library. Statically compiled files are much easier > > to work with, but Python is too dynamic to be fully statically > > compiled. > > > > - David > > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Jython-users mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-users > |
From: Michael H. <mi...@hu...> - 2008-03-04 16:50:41
|
thanks for your explanations!! The Python web site states this (dynamic and static compilation) as a major difference to other dynamically typed languages ... but I'm not sure about that .. as far as I know Groovy does this similar .. ?! .. this approach is very interesting .. Michael > On Tue, Mar 4, 2008 at 6:03 PM, Michael Hüttermann > <mi...@hu...> wrote: >> this means that Jython is either statically compiled *or* dynamically >> compiled *or* not compiled in the runtime environment? These are the >> three >> possibilities? >> >> Thanks !!! >> > > Basically you have interpreted vs compiled. Compilation can be further > branched down to statically vs dynamically compiled. As David already > said basically statical vs dynamical compilation is the same process > but applied at different moment and with a small difference on the > output (statical: there is a compilation step during the build > process, it generally results in a specific output -- in the JVM case > compilation leads to .class files; dynamic: there is not a separate > compilation step involved during the build process, but rather this is > done during the execution of the program, and the output (in the case > of JVM) is still bytecode but not in the form a files, but rather > bytecode that gets loaded into the VM). > > cheers, > > ./alex > -- > .w( the_mindstorm )p. >> >> >> >> >> > Static compilation is done at compile-time, creating Java class files >> > (.class files) that can be deployed and loaded like any other class >> > files, by code that doesn't know anything about Jython. Dynamic >> > compilation happens at runtime and must be initiated by code that >> > calls the Jython library. Statically compiled files are much easier >> > to work with, but Python is too dynamic to be fully statically >> > compiled. >> > >> > - David >> > >> > >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Jython-users mailing list >> Jyt...@li... >> https://lists.sourceforge.net/lists/listinfo/jython-users >> > |
From: A. P. ☀ <the...@gm...> - 2008-03-04 17:12:59
|
On Tue, Mar 4, 2008 at 6:50 PM, Michael Hüttermann <mi...@hu...> wrote: > thanks for your explanations!! > > The Python web site states this (dynamic and static compilation) as a > major difference to other dynamically typed languages ... but I'm not sure > about that .. as far as I know Groovy does this similar .. ?! .. this > approach is very interesting .. > > Michael > You are right. Groovy support both statical and dynamic compilation. Each have their advantages (f.e. static compilation is useful for distributing packaged apps without the need to distribute sources; dynamic compilation is useful for quickly running your scripts/apps). However, Groovy doesn't have an interpreted-mode. hth, ./alex -- .w( the_mindstorm )p. > > > > > > On Tue, Mar 4, 2008 at 6:03 PM, Michael Hüttermann > > <mi...@hu...> wrote: > >> this means that Jython is either statically compiled *or* dynamically > >> compiled *or* not compiled in the runtime environment? These are the > >> three > >> possibilities? > >> > >> Thanks !!! > >> > > > > Basically you have interpreted vs compiled. Compilation can be further > > branched down to statically vs dynamically compiled. As David already > > said basically statical vs dynamical compilation is the same process > > but applied at different moment and with a small difference on the > > output (statical: there is a compilation step during the build > > process, it generally results in a specific output -- in the JVM case > > compilation leads to .class files; dynamic: there is not a separate > > compilation step involved during the build process, but rather this is > > done during the execution of the program, and the output (in the case > > of JVM) is still bytecode but not in the form a files, but rather > > bytecode that gets loaded into the VM). > > > > cheers, > > > > ./alex > > -- > > .w( the_mindstorm )p. > >> > >> > >> > >> > >> > Static compilation is done at compile-time, creating Java class files > >> > (.class files) that can be deployed and loaded like any other class > >> > files, by code that doesn't know anything about Jython. Dynamic > >> > compilation happens at runtime and must be initiated by code that > >> > calls the Jython library. Statically compiled files are much easier > >> > to work with, but Python is too dynamic to be fully statically > >> > compiled. > >> > > >> > - David > >> > > >> > > >> > >> > >> ------------------------------------------------------------------------- > >> This SF.net email is sponsored by: Microsoft > >> Defy all challenges. Microsoft(R) Visual Studio 2008. > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> _______________________________________________ > >> Jython-users mailing list > >> Jyt...@li... > >> https://lists.sourceforge.net/lists/listinfo/jython-users > >> > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Jython-users mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-users > |