Aha! i see what you are saying thank you for pointing the real
subtleness of the way command is return,
this group is really excellent and awesome in helpfullness
On Aug 6, 11:51 am, Armando Blancas wrote:
> In addition to that, prnTime should have no parens:
> #(on-thread prnTime)
>
> As it was,
In addition to that, prnTime should have no parens:
#(on-thread prnTime)
As it was, prnTime was running before going into on-thread, which was
acting on a runnable that's nil (the return value of prn). The
difference between the two can be seen in the output. When prnTime
runs inside the threads,
What do you mean "close threads"?
As I know threads aren't supposed to be closed. There is no mechanism to do
this. They are not connections or smth like that.
On Fri, Aug 6, 2010 at 3:46 PM, foop1 wrote:
> thank you for the reply, is there any way to close this 4 threads
> after the job is done
thank you for the reply, is there any way to close this 4 threads
after the job is done?
On Aug 6, 8:34 am, Nikita Beloglazov wrote:
> Hi, foop
> Your error in this line:
> (r4t (on-thread (prnTime)))
> You pass to function r4t thread instead of functions. Because
> (on-thread (prnTime)) returns
Hi, foop
Your error in this line:
(r4t (on-thread (prnTime)))
You pass to function r4t thread instead of functions. Because
(on-thread (prnTime)) returns thread
You must pass #(on-thread (prnTime)) instead
Regards,
Nikita Beloglazov
On Fri, Aug 6, 2010 at 3:13 PM, foop1 wrote:
> Hi,
>
> Iam try
