You explained me that. Thank you :)
--
You received this message because you are subscribed to the Google Groups
"mechanical-sympathy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mechanical-sympathy+unsubscr...@googlegroups.com.
For more options, vi
, 2017 at 1:57 AM, Remi Forax wrote:
>
>
> --
>
> *De: *"John Hening"
> *À: *"mechanical-sympathy"
> *Envoyé: *Lundi 13 Novembre 2017 00:17:32
> *Objet: *Executing thread by JVM.
>
> Hello,
>
>
> I would like to as
> De: "John Hening"
> À: "mechanical-sympathy"
> Envoyé: Lundi 13 Novembre 2017 00:17:32
> Objet: Executing thread by JVM.
> Hello,
> I would like to ask for threads in Java. As we know, JVM uses system threads
> (native threads). So, for example i
Hey John,
Without commenting on whether threads in Java are always tied to native
threads (I don't think this is always strictly true), sounds like there
might be a misunderstanding here. What is special about threads in
particular that make you think `any_code` wouldn't be JIT-able here? Put
anot
Hello,
I would like to ask for threads in Java. As we know, JVM uses system threads
(native threads). So, for example it uses Linux threads. In simplification a
thread is a stack + piece of code to execute.
Let's consider:
Thread t = new Thread(() -> {`any_code`});
t.start();
t.join();
