Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #19797
| From | Bernd Paysan <bernd.paysan@gmx.de> |
|---|---|
| Newsgroups | comp.lang.forth |
| Subject | Re: Locals with a broader scope |
| Date | 2013-02-18 17:29 +0100 |
| Organization | 1&1 Internet AG |
| Message-ID | <kftkts$vqa$1@online.de> (permalink) |
| References | <a3216023-8480-4845-9975-2e28c763beef@googlegroups.com> <0fb56fee-bbe8-4ed4-8b28-3e59d2520cf4@googlegroups.com> <__idnTtoCNkWRLzMnZ2dnUVZ_gSdnZ2d@supernews.com> <qPqdnXqGq9TiabzMnZ2dnUVZ_sqdnZ2d@supernews.com> |
Andrew Haley wrote: > Well, I know what you mean, kinda sorta, but the world has changed. > Processors with more than one core are common now, even in many > embedded designs. To program such computers effectively really > requires multi-tasking and re-eentrant coding. That standard Forth > still doesn't address this is a shortcoming. Standard Forth has no multitasking wordset. There is some common practise, and for task-specific variables, we use USER <name>. I tend to use current-object OOP for this purpose. The current object is in a user variable or register (depends on what is available), and points to a structure; polymorphic methods aren't needed for that; the access is similar to normal variables (could also be locals with auto-fetch and to). We should accept that any scope bigger than a single word in Forth is indeterminated, so it should be a (potentially) long-living object that contains those information. -- Bernd Paysan "If you want it done right, you have to do it yourself" http://bernd-paysan.de/
Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Locals with a broader scope Brad Eckert <hwfwguy@gmail.com> - 2013-02-16 10:40 -0800
Re: Locals with a broader scope Brad Eckert <hwfwguy@gmail.com> - 2013-02-16 13:50 -0800
Re: Locals with a broader scope anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2013-02-17 13:24 +0000
Re: Locals with a broader scope Andrew Haley <andrew29@littlepinkcloud.invalid> - 2013-02-17 09:47 -0600
Re: Locals with a broader scope anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2013-02-18 13:40 +0000
Re: Locals with a broader scope "Elizabeth D. Rather" <erather@forth.com> - 2013-02-17 21:34 -1000
Re: Locals with a broader scope Andrew Haley <andrew29@littlepinkcloud.invalid> - 2013-02-18 03:29 -0600
Re: Locals with a broader scope Bernd Paysan <bernd.paysan@gmx.de> - 2013-02-18 17:29 +0100
Re: Locals with a broader scope albert@spenarnc.xs4all.nl (Albert van der Horst) - 2013-02-18 12:05 +0000
Re: Locals with a broader scope anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2013-02-18 14:39 +0000
Re: Locals with a broader scope Brad Eckert <hwfwguy@gmail.com> - 2013-02-18 09:04 -0800
Re: Locals with a broader scope Percy <percival.andrews@gmail.com> - 2013-02-19 02:33 -0800
Re: Locals with a broader scope anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2013-02-19 11:25 +0000
Re: Locals with a broader scope Andrew Haley <andrew29@littlepinkcloud.invalid> - 2013-02-19 11:42 -0600
Re: Locals with a broader scope Bernd Paysan <bernd.paysan@gmx.de> - 2013-02-17 02:00 +0100
Re: Locals with a broader scope Doug Hoffman <glidedog@gmail.com> - 2013-02-17 16:51 -0500
Re: Locals with a broader scope "A. K." <akk@nospam.org> - 2013-02-18 07:58 +0100
Re: Locals with a broader scope Brad Eckert <hwfwguy@gmail.com> - 2013-02-19 09:20 -0800
Re: Locals with a broader scope Brad Eckert <hwfwguy@gmail.com> - 2013-02-22 08:27 -0800
csiph-web