Time for action - using whos
We are working with quite a few variables now. We can list them all with whos:
octave:48>whos Variables in the current scope:
Attr |
Name |
Size |
Bytes |
Class | |
==== |
==== |
==== |
===== |
===== | |
A |
2x2 |
32 |
double | ||
B |
2x2x2 |
128 |
double | ||
T |
2x6 |
12 |
char | ||
Z |
2x2 |
64 |
double | ||
a |
1x1 |
8 |
double | ||
ans |
1x9 |
9 |
char | ||
b |
1x5 |
40 |
double | ||
c |
3x1 |
24 |
double | ||
d |
1x12 |
96 |
double | ||
projectile |
1x3 |
42 |
cell | ||
projectiles |
2x3 |
83 |
cell | ||
s |
1x2 |
83 |
struct | ||
t |
1x11 |
11 |
char | ||
z |
1x1 |
16 |
double |
Total is 81 elements using 648 bytes
What just happened?
As seen above, whos
prints out five columns. The first column can have values g
or p
, which means that the variable is global or persistent. We shall return to what these qualifiers mean in Chapter 5. In our case, all the variables are what are named local, which is not stated explicitly by the command whos
. A local variable is characterized by being visible and therefore accessible to a given workspace...