Re^2: Daemonized perl and clearing variables...

Replies are listed 'Best First'.
Re^3: Daemonized perl and clearing variables... by 5mi11er (Deacon) on May 30, 2013 at 12:30 UTC
How do you know the "compiling" didn't break your code? What happens when you run the non-compiled code? -Scott	[reply]
Re^4: Daemonized perl and clearing variables... by ali_kerem (Acolyte) on May 30, 2013 at 13:02 UTC
That is really hard question. Because I didn't run non-compiled code for a while ( almost two months ) and I changed the code many times, here and there etc. But when I think of it, compiled OR non-compiled code both were running good from command line before and even now sometimes it works for 2-3 hours, just randomly stops. Only thing compilation gives is a warning ( perl perlc -bleach -exe /myScript/APP/myScript myScript.bin ); `Out: myScript.bin.c myScript.bin.c: In function āmainā: myScript.bin.c:40456: warning: ISO C90 forbids mixed declarations and +code Exe: /myScript/APP/myScript` [download]	[reply] [d/l]
Re^5: Daemonized perl and clearing variables... by marto (Cardinal) on May 30, 2013 at 13:16 UTC
"But when I think of it, compiled OR non-compiled code both were running good from command line before" Before what? What has changed? perl āmainā ISO C90 forbids mixed declarations, āmainā ISO C90 forbids mixed declarations. Are you sure it's not worth while running a normal version of your code to debug/see where it's falling over?	[reply]
Re^6: Daemonized perl and clearing variables... by ali_kerem (Acolyte) on May 30, 2013 at 13:51 UTC