freenode/#ecl - IRC Chatlog

9:58:15 mitigate is there some recommended way to ext:exit from code when building an executable I dont want to exit when compiling or loading, but only exit when the program runs

9:58:25 mitigate some way to call

9:58:44 mitigate pinch can do (unless (or *compile-file-pathname* *compile-file-truename* *load-pathname* *load-truename*) (ext:exit))

9:59:47 jackdaniel what about epilogue-code ?

9:59:53 mitigate ah

10:00:48 mitigate I'm not using asdf but i'll see if it can work

10:01:02 jackdaniel epilogue-code may be passed to build-program directly I think

10:01:31 jackdaniel also when you have a function to run (i.e toplevel-function) and it ends, program will end by itself

10:10:55 mitigate i built clang for the first time.. c2ffi is pretty cool. I dont think i'll be checking out clasp though

11:40:20 mitigate :epilogue-code also helps, thanks

11:40:48 mitigate I spoke too soon about c2ffi. it's not grokking most of the linux stuff

11:42:20 mitigate i tried profiling how long it takes for ecl to load when ecl is linked in via a shared-library and then loads a bundle - when the bundle is compiled to a fasl and ecl calls load on it, - and when the bundle is compiled to a shared-library and calling dlopen on it. both take the about same time - around 15 seconds on this box

11:42:54 mitigate now when i tried a standalone exe (a different situation) but i see it takes about the same amount of time when i build-program with that bundle contents. i guess its all the same loading mechanism underneath

11:51:08 jackdaniel there are different mechanisms, but there is a common code to populate toplevel forms which takes most of the time

11:51:23 jackdaniel so the longest part is indeed shared