Subject:
|
Pseudocode
|
Newsgroups:
|
lugnet.robotics.handyboard
|
Date:
|
Fri, 19 Sep 1997 10:31:10 GMT
|
Original-From:
|
jackedIN <jackedIN@#avoidspam#earthlink.net>
|
Viewed:
|
1298 times
|
| |
|
|
Hello,
Im very new to the list and to the entire concept of all of it basically.
but- i'll cut to the chase (its breif)
Just learning c programming i ran across a chapter in the book which
explains pseudocode and its impact. I dont know how many programmers are on
the handyboard list, or even if this msg is worth replying to OR even if
flow charts and psuedocode are still in practice. But, i have always been
confused about this...
If i design a simple robot that simply (to some ppl, heh) moves around on
the floor scanning for things so it may take appropriate action to avoid
hitting them, just how would someone program that.
Psuedocode is a layout of the control of the program. But, if the robot
does the same thing over and over again with no real output....??
NO- i am not confusing pseudocode with the actual C language (as pseudocode
is NOT a programming lang) basically im asking for some simple pseudocode
from someone so that i can better understand both linear thinking in terms
of a robot and the impact a pseudocode has on the implimentation into the
actual program...
-im sure this makes NO sense to a good portion, and thats my fault heh-
_/_/_/_/a cyberNETix organiZM_/_/_/_/
http://home.earthlink.net/~jackedin
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
|
|
Message has 1 Reply:
 | | Re: Pseudocode
|
| (...) One thing to remember: the input is the world (through the sensors) and the output are the robots actions on the world. A program outline repeat turn on drive motors repeat read wall/obstacle sensor until sensor reads an obstacle stop motors (...) (27 years ago, 19-Sep-97, to lugnet.robotics.handyboard)
|
3 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
