Ti89 Titanium too few arguments

  • Thread starter Thread starter Spagnum
  • Start date Start date
  • Tags Tags
    Titanium
Click For Summary

Discussion Overview

The discussion revolves around issues encountered while using the mod( function on the TI-89 Titanium calculator, as well as programming challenges related to calculating the area of a sector. Participants share their experiences, troubleshooting steps, and code snippets, focusing on both calculator functionality and programming syntax.

Discussion Character

  • Technical explanation
  • Homework-related
  • Debate/contested

Main Points Raised

  • One participant reports receiving a "too few arguments" error when attempting to use the mod( function, expecting it to work similarly to other calculators.
  • Another participant suggests using the correct syntax mod(54,10) to resolve the issue.
  • A participant mentions that the error persists despite using the suggested syntax and resetting the calculator.
  • There is a discussion about potential issues with argument separators, with one participant suggesting that the use of a decimal point instead of a comma might be causing the error.
  • One participant confirms that switching from a period to a comma resolved their issue with the mod( function.
  • A separate participant shares a programming challenge related to calculating the area of a sector, also encountering a "too few arguments" error in their code.
  • Another participant points out a missing comma in the code, which could be the source of the error.
  • Further suggestions include ensuring that dialog functions return values correctly and optimizing variable declarations in the program.

Areas of Agreement / Disagreement

Participants generally agree on the importance of using the correct syntax for functions and the potential for errors due to punctuation. However, there are multiple views on programming practices and the specific issues encountered, indicating that the discussion remains unresolved in some aspects.

Contextual Notes

Limitations include potential misunderstandings regarding the use of argument separators and the handling of dialog functions in programming, which may vary based on individual experiences with the calculator.

Spagnum
Messages
4
Reaction score
0
Ti89 Titanium "too few arguments"

sorry for my noobieness, but I'm having problem with my mod( function on my Ti89 Titanium

On other calcs: 54 mod 10 = 4
like here: http://www.google.com/search?q=54+mod+10

But when i use the mod( function I either get "to few arguments" og just the result 54.mod10

can anyone point me to what I'm doing wrong?
 
Last edited by a moderator:
Computer science news on Phys.org


Welcome to PF, Spagnum! :smile:

Have you tried mod(54,10)?
 


Thank you!

yes I have - that just results in "Too few arguments"
 


Yup I been to that page myself but I get the same result.(Too few arguments) I even reset the calculator, in case it had something to do with some settings.
 


Spagnum said:
Yup I been to that page myself but I get the same result.(Too few arguments) I even reset the calculator, in case it had something to do with some settings.

The one reason I can think it might say "too few arguments", is if there's a problem with the decimal point, in which case you'd have tried to calculate mod(54.10, ?)
You sure you used a comma?
Or perhaps you could try a semicolon?
 


ofc... the comma. :blushing:
I'm so use to working in Excel where . is the comma, and haven't used my calculator in ages.

Anyways it works like a charm now, thanks a lot for your help Serena!
 


You're welcome! :smile:
 


On my TI-89 (but not Titanium) mod(54,10) gives correct 4.
 
  • #10


The old UK versus USA, comma versus period switcheroo, eh? :rolleyes:
 
  • #11


Uhh :rolleyes: I've never heard of using a period as an argument separator? :confused:
 
  • #12


Hey I am also a noob and I need help.
I made this program to calculate the area of a sector and I keep getting "Too Few Arguments"
The ø is a theta and the 'arrow' is the arrow made by STO


area_sec()
Prgm
Local a,r,g,s,ø,k
Dialog
Request "Press 1 if you have rs and 2 if you have rø"a
EndDlog
If a=1 Then
Dialog
Request "Enter r",r
Request "Enter s",s
EndDlog
expr(-r) 'arrow' r
expr(s) 'arrow' s
(1/2)*r*s 'arrow' k
Disp "Area is"&string(k)
Else If a=2 Then
Dialog
Request "Enter r",r
Request "Enter ø",ø
Dialog
expr(-r) 'arrow' r
expr(s) 'arrow' s
(1/2)*r*r*ø 'arrow' k
Disp "Area is"&string(k)
Else
EndIf
DelVar a,r,s,ø,k
EndPrgm
 
  • #13


Look at line 5 again:

Request "Press 1 if you have rs and 2 if you have rø"a

You forgot a comma in between your "request" and your variable, like so:

Code:
Request "Press 1 if you have rs and 2 if you have rø"[B],[/B]a

Try that and see what you get.
 
  • #14
SonikkuUSA is right about the comma. Also, after the first "EndDlog", you have to add "expr(a)->a". This is because request (and any dialog function) is treated as a string, and we want a value. Also, in the first request, type"Request"Words",a,0. The zero will turn alpha-lock off in that box so you don't have to hit the alpha button every time you want to type 1.

Instead of using delvar at the end, you could just use local and define all of the variables at the beginning, too.
 

Similar threads

  • · Replies 1 ·
Replies
1
Views
9K
  • · Replies 52 ·
2
Replies
52
Views
6K
  • · Replies 2 ·
Replies
2
Views
2K
Replies
9
Views
9K
  • · Replies 2 ·
Replies
2
Views
2K
  • · Replies 9 ·
Replies
9
Views
3K
Replies
7
Views
2K
  • · Replies 5 ·
Replies
5
Views
4K
Replies
4
Views
2K
  • · Replies 14 ·
Replies
14
Views
2K