> > Other than speed, the metric most often important in evaluating an
> algorithm is:
> > a) memory consumption.
> > b) code space.
> > c) source code language.
> > d) use of floating point operations.
>=20
> Yuk! this depends *very* much on the area of application! I guess a shoul=
d
> be RAM consumption, or is it ambigu by design?

That is my reaction as well. Is code space considered as ROM, or are we tal=
king as being on a mainframe here, in which case a and a are equivalent (an=
d therefore confusing). Or maybe the answer is a and b are considered alway=
s both correct.



--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.