assignment

G

Gedeon Mkangumbe

1.what are the properties of pseudocode
2. Explain array its types
3.What is dry running
 
O

osmium

Gedeon Mkangumbe said:
1.what are the properties of pseudocode

I think the Wikipedia article is probably better than some ad hoc thing
someone here is likely to type in in a few idle minutes. Focus on the first
two or three paragraphs. Wikipdeia is often a good first place to look for
computer oriented problems, especially of this sort.

http://en.wikipedia.org/wiki/Pseudocode
2. Explain array its types

An array is composed of _elements_. The elements of an array must be
homogeneous. Does that help?
3.What is dry running

Long, long ago people used to try to visualize what happened when the mental
image of a program was conjured up in the mind. Perhaps this is what your
instructor is thinking of, perhaps not. I think this technique has lost
popularity what with everyone having a computer or two on every desktop.
Kind of like an arranger visualizing how music would sound - except no
orchestra.
 
J

Jorgen Grahn

"Gedeon Mkangumbe" wrote:
[redacted]
Dude, don't do this idiot's homework for him!!!

He didn't -- he just gave him pointers to information and hints.
(Telling him not to post general programming questions here would have
been nice too.)

/Jorgen
 
J

Jorgen Grahn

: ....

Long, long ago people used to try to visualize what happened when the mental
image of a program was conjured up in the mind.

Don't know about you, but to me this is still a vital technique. Maybe
not /literally/ acting as an interpreter, but at least reading and
analyzing a piece of code until I'm convinced it works. Sometimes that
means running a few loops in my head or on pen and paper.

"Convinced it works" is often more than unit tests can deliver.
Perhaps this is what your
instructor is thinking of, perhaps not. I think this technique has lost
popularity what with everyone having a computer or two on every desktop.
Kind of like an arranger visualizing how music would sound - except no
orchestra.

/Jorgen
 
B

BCFD36

Boardwalk and Park Place.


An excellent Bruce Dern film of the early 1970s... no, wait that doesn't
sound right.
No, that was Silent Running. I saw it in a drive-in with two other guys.
We discussed why Pam wouldn't sleep with Steve (we were juniors in high
school) and drank lots of beer. Pam was hot at 17 and is still hot at
56. Good movie.
 
B

BGB

Don't know about you, but to me this is still a vital technique. Maybe
not /literally/ acting as an interpreter, but at least reading and
analyzing a piece of code until I'm convinced it works. Sometimes that
means running a few loops in my head or on pen and paper.

"Convinced it works" is often more than unit tests can deliver.

apparently, the ability to do stuff like this can also confuse some
people as well.


it is sometimes useful.

sometimes a person can run and debug a code fragment in their head
faster than it would take to recompile the app and proceed to test the
code manually.

for tiny apps, maybe it is harder to justify, but for less trivial apps,
it can sort of become an issue where nearly every rebuild is an
opportunity for a coffee break, and sometimes the relevant test-cases
may be a hassle to set up (involve some edge case behavior or similar).

one may at least make basic mental effort to verify it will probably
work before waiting through the recompile and test process (or,
sometimes, one will note that there is a serious bug partway through the
rebuild, then abort the compile, fix the bug, and start the rebuild over
again).


or such...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,744
Messages
2,569,483
Members
44,903
Latest member
orderPeak8CBDGummies

Latest Threads

Top