On Thu, 2005-04-28 at 10:00, Luke Palmer wrote:
Aaron Sherman writes:
Well, more to the point, autothreading of junctions will hit the wall of
Parrot duping the interpreter. That's probably not something you want to
suffer just to resolve a junction, is it?
What? Why will it do that?
On Thu, Apr 28, 2005 at 12:46:53PM -0400, Aaron Sherman wrote:
On Thu, 2005-04-28 at 10:00, Luke Palmer wrote:
Aaron Sherman writes:
Well, more to the point, autothreading of junctions will hit the wall of
Parrot duping the interpreter. That's probably not something you want to
Aaron Sherman wrote:
On Thu, 2005-04-28 at 10:00, Luke Palmer wrote:
Aaron Sherman writes:
Well, more to the point, autothreading of junctions will hit the wall of
Parrot duping the interpreter. That's probably not something you want to
suffer just to resolve a junction, is it?
On Thu, 2005-04-28 at 13:55, Rod Adams wrote:
I would be dismayed if autothreading used threads to accomplish it's
goals. Simple iteration in a single interpreter should be more than
sufficient.
Sorry, I misunderstood. Thanks for the clarification.
--
Aaron Sherman [EMAIL PROTECTED]
RA == Rod Adams [EMAIL PROTECTED] writes:
RA I would be dismayed if autothreading used threads to accomplish it's
RA goals. Simple iteration in a single interpreter should be more than
RA sufficient.
how autothreading is implemented is distinct from the language
feature. a simple version
Rod Adams wrote:
I would be dismayed if autothreading used threads to accomplish it's
goals. Simple iteration in a single interpreter should be more than
sufficient.
For sure. No point in doing 10_000 cycles to set up a scratch area
for a single boolean test that might take 10 cycles.
A
