home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.hp48
- Path: sparky!uunet!tcsi.com!iat.holonet.net!brianw
- From: brianw@iat.holonet.net (Brian Walsh)
- Subject: Re: Passing Functions as Parameters
- Message-ID: <BxHp7z.LML@iat.holonet.net>
- Organization: HoloNet (BBS: 510-704-1058)
- References: <6596@dciem.dciem.dnd.ca>
- Distribution: na
- Date: Tue, 10 Nov 1992 07:38:22 GMT
- Lines: 24
-
- jorchard@dciem.dciem.dnd.ca (Jeff Orchard) writes:
- : I would like to be able to put 'F' in level 1 and then execute the
- : program. I DON'T want to have to put 'F(X)' on the stack... because that
- : would force me to integrate with respect to X. It would be nice if
- : I could integrate with respect to a local variable.
- :
- : OR... my problems would be solved if I could change this... "F(X)"
- : to this... 'F(X)'
-
- Use APPLY:
- 1) { X } 'F' APPLY ==> 'F(X)'
- 2) { Y Z } 'G' APPLY ==> 'G(Y,Z)'
-
- Then EVAL, etc. The quick reference guide lists the input arguments in
- incorrect order.
-
- "F(X)" OBJ-> doesn't work and results in an error, and using #5B15h
- SYSEVAL to create a name from a string is also wrong. You want to create
- an symbolic expression, not a global variable name, and their structures
- are entirely different. APPLY's raison d'etre.
-
- -- Brian Walsh
- brianw@holonet.net
-
-