 | | How to make shared memory....not —Michael Obenland
|
| | | (...) You ask for it, you get it. BUT: It works, sort of. It will not survive any multitasking problems. Shared memory has to be handled by the OS, not by a user program. I split your problem to 3 programs. Program 1 allocates the memory and prints (...) (23 years ago, 22-Dec-01, to lugnet.robotics.rcx.legos)
|
| | | |
| | | | | Re: How to make shared memory....not —Steve Hassenplug
|
| | | | (...) Thanks, Michael. This appears to be exactly what I'm looking for. I assume if I want to store more values, I can just change the 'shared' struct, right? (add l, m, n...) When you say 'multitasking problems', you're talking about storing & (...) (23 years ago, 27-Dec-01, to lugnet.robotics.rcx.legos)
|
| | | | |
| | | | | | Re: How to make shared memory....not —Michael Obenland
|
| | | | (...) Yes. That is the only thing you have to do. You can store whatever you want. (...) Exactly. If you know you what you do, nothing bad can happen. BTW., this scheme can be extended to something like a shared library. If you store pointers to (...) (23 years ago, 27-Dec-01, to lugnet.robotics.rcx.legos)
|
| | | | |
| | | | | | Re: How to make shared memory....not —Steve Hassenplug
|
| | | | (...) ooohh. I like that idea. So I can write one program with all my functions and my other programs can just include a couple function calls. Again, in my VB world, I don't mess with pointers. When you have a minute, can you type up a sample (...) (23 years ago, 27-Dec-01, to lugnet.robotics.rcx.legos)
|
| | | | |
| | | | | | Re: How to make shared memory....not —Andy Gombos
|
| | | | | I think this is what you want, but I am still learning. :) int inc (int&); int dec (int&); int (*pFunc) (int); //pointer to a function that accepts/returns an int if (add) { pFunc = inc; } else { pFunc = dec; } int a = pFunc(10); So, if add is true, (...) (23 years ago, 27-Dec-01, to lugnet.robotics.rcx.legos)
|
| | | | | |
| | | | | | | Re: How to make shared memory....not —Steve Hassenplug
|
| | | | | | (...) Yes, I'm sure I can. And I think it would be 'safer' that way. But Mike's idea about functions sounds interesting. I don't really have any idea about how I would use that in a real program, but it sure sounds interesting. Steve (23 years ago, 27-Dec-01, to lugnet.robotics.rcx.legos)
|
| | | | | | |
| | | | | | Re: How to make shared memory....not —Michael Obenland
|
| | | | Hi Steve, (...) Yes. Actually, I am working on a robot that finds a path trough a maze. After solving the maze, a second program can run through the maze with the informations from the first program. (I will do this with shared mem). Both programs (...) (23 years ago, 28-Dec-01, to lugnet.robotics.rcx.legos)
|
| | | | |
