| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | threads, threads, more th |
[...] JL> display other). I use the /same/ thread function for all threads. JL> JL> Is this OK to do? Are there any situations in which my program JL> would behave erroneusly? JL> JL> [...] Multiple threads can share the same code with no problem. You just need to keep data spaces straight. Any global or static data are shared by all threads. Automatic data are on the stack and each thread has its own stack. There's a "thread" (or "_thread") keyword that produces a thread-private data store, but I've not used it. Anyway, if your threads 'share' variables in memory, you may need to serialize access to these data via the use of mutex semaphores. I glanced at your code and saw no problems (but I often see no problems w/ my code until I get it under the debugger :-) hank þ KWQ/2 1.2g NR þ "640K ought to be enough for anybody." - Bill Gates, 1981 --- WM v2.04/92-0551* Origin: GREATER CHICAGO Online!! (708) 895-4083 (1:115/895) SEEN-BY: 12/2442 54/54 620/243 624/50 632/348 640/820 690/660 711/409 410 413 SEEN-BY: 711/430 807 808 809 934 712/353 623 713/888 800/1 @PATH: 115/895 109/347 2 1 3615/50 229/2 12/2442 711/409 54/54 711/808 809 @PATH: 711/934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.