Abridged summary of comp.lang.tcl@googlegroups.com - 14 updates in 5 topics

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Abridged summary of comp.lang.tcl@googlegroups.com - 14 updates in 5 topics

comp.lang.tcl mailing list
Jim <[hidden email]>: Jan 15 01:40PM -0800

> Jim, would be possible to write this kind of command?
 
> proc noop {args} {}
> proc threadit {num args} {LITERAL BLACK MAGIC NUM TIMES}
 
Absolutely! Yes, great question.
 
There is one such ...more
Rich <[hidden email]>: Jan 15 10:09PM

> it actually -- so I'm hoping somebody that has might join in and
> contribute that code to this effort. I just know its possible and would
> love to collaborate with somebody on solving it.
...more
[hidden email]: Jan 15 06:10PM -0800


> However, the obstacle seems easily overcome if community pages existed that shared some basic concepts and conventions (example code) so that folks get this info/training upfront. ...more
Rich <[hidden email]>: Jan 16 03:07AM

> this example.
 
> I think it would be cool to see this implemented using threads to get
> the expected results.
 
The reason you get the differing effect you see is that vwaits nest, ...more
[hidden email]: Jan 16 12:32AM -0800

On Monday, January 15, 2018 at 7:07:47 PM UTC-8, Rich wrote:
 
> Alternately, if you really need a 'stop and wait here while the event
> loop continues before continuing' then that would be a ...more
Rich <[hidden email]>: Jan 16 10:49AM

> delays (an androwish tcl program I wrote to control my Roku device).
> It's much easier to write (and especially to read) using sequential
> wait commands.
 
Which is why I also said: "While it ...more
"Donal K. Fellows" <[hidden email]>: Jan 16 01:11PM

On 16/01/2018 10:49, Rich wrote:
> If you want to keep the synchronous style, but have asynchronous
> operation (event loop) then using 8.6 and coroutines are the superior
> way to go.
...more
[hidden email]: Jan 16 10:03AM -0800

On Tuesday, January 16, 2018 at 5:11:10 AM UTC-8, Donal K. Fellows wrote:
 
> you get sensible control flow with very little script-level overhead, so
> your code writes pretty much the same (OK, ...more
Rich <[hidden email]>: Jan 16 06:30PM

>> same pattern) as a synchronous wait yet without the bad side effects.
 
> Interesting. Could you provide an example that demonstrates how one
> might write a co-routine with a wait, in as few ...more
[hidden email]: Jan 16 12:09PM -0800

On Tuesday, January 16, 2018 at 10:30:12 AM UTC-8, Rich wrote:
 
 
Thanks for the detailed reply.
 
 
 
> That one is easy, although I am assuming you mean a tk or ttk "button"
> and not an lirc ...more
"Ricardo kozmate.net" <[hidden email]>: Jan 16 10:03AM

Em 15/01/18 12:07, Andre escreveu:
> set c [join a$b {}] ;#doesnt work (the result is incorrect)
 
Also, I'd say the result was not "incorrect", the result was "unexpected".
 
That is, you better ...more
Nicolas <[hidden email]>: Jan 15 11:32PM -0800

thank you very much Keith
 
best regards,
Nicolas
 
Le lundi 15 janvier 2018 20:16:58 UTC+1, Keith Nash a écrit :
...more
Ali M <[hidden email]>: Jan 15 09:32PM -0800

On Saturday, January 13, 2018 at 1:49:34 PM UTC-5, Gerald Lester wrote:
 
> > In the #tcl irc channel it is derided as abandoned. A couple days ago I got the idea for a distributed software ...more
stefan <[hidden email]>: Jan 15 01:50PM -0800

> Why not use Apache Httpd (which is one of the most widespread servers
> out there)?
 
I might be wrong here, but last time I checked, Apache Rivet required prefork MPM and, alas, Apache's ...more
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to [hidden email].