First off, I am thankful for the attention being paid to this topic of
mine. Thanks to one of you for the link to the NSpire manual. I teach
both math and computer science, and one of the basic things we teach
in Comp Sci is that all programs must have an input and an output.
That is, they most often require some interaction with the end user. I
thus consider the lack of an input statement a glaring omission.
I agree with you that there are a whole host of new functions, and the
presence of user-defined functions, if they can be actually called in
programs or stored in a library, is a great tool with great
possibilities.
What you have suggested appears to be to fill out a table and then run
the program. This is a great suggestion, however, this can also be
done on both my TI-83 and my TI-84. Admittedly, it was something that
I hadn't thought of at the time. The greater reason for programming
the claculator the way I did was to teach myself the language, as well
as giving me a quick-and-dirty method for calculating class averages
on tests without having to fire up my laptop and starting a
spreadsheet. (to those who are curious, this is not a straightforward
job -- our marks are based on a weighted system which I don't want to
get into, which I am not sure anyone beyond us math teachers really
get).
I think it has to be generally admitted that the loss of the input
statement results in a sacrifice in flexibility. Programmable
calculators have existed since the 1980s which can accept keyboard
input. I like to teach myself how to write programs in several
languages, and if a language lacks a means of input, then just to get
on to the ground level, I would have to learn about how the program
interacts with tables, and other applets in the system, as well as the
quirks in each of the applets. Someone on this list suggested that the
columns in the tables have to be named before they are used. If the
program uses the same names, does that mean that I have to rename the
columns if I accidentally delete the spreadsheet page? Or can I save a
template of a table with the names I want?
Doing repeated claculations (the original reason for programmable
calculators) now must be done on tables, but I still think that
calculations should be made possible on direct input. That just seems
more intuitive to me, and provides a good holdover until I feel more
confident with tables.
Phrank
On Dec 20, 7:49 pm, "Nelson Sousa" <
nso...@gmail.com> wrote:
> yes, the 10 elements were just an example. Of course you can have lists of
> (almost) any size. I mean, I just created a list of 10 thousand elements on
> my Nspire and it did ok (what's the limit, by the way? anybody knows?).
>
> But for what you want to do I believe it's much simpler to just insert the
> data on a spreadsheet. I only use programs if I have no other choice,
> otherwise I prefer to use simpler tools. Also on a spreadsheet you can edit
> the values later on and correct them, while on the code you provided there's
> no possibility of changing a number once entered (and isn't it easy to type
> it wrong when you're inserting 20 or 30 numbers in a row...).
>
> The main limitations beetwen programing for the 84+ and for Nspire is that
> all input must be given when you call the program, you can't have inputs in
> the middle of the code, and all output must be made sequentially as a set of
> Disp instructions, not allowing you to output a string, then delete it and
> output a different one, etc.
>
> But there are a lot of advanced features, inherited from 89 Titanium/Voyage
> 200 programming language, that make the difference, and add significant
> programming power.
>
> My view, to wrap it up, is that Nspire is so complex that one must really
> take the time to explore it fully before concluding about what can or can't
> be done. I mean, some of the stuff you see here weren't even possible in
> one's wildest dreams just a few months ago!
>
> Nelson
>