home *** CD-ROM | disk | FTP | other *** search
-
- TTX <=> SAS/C
- Version 2.1
-
- These macros and the accompanying TurboText definition file are all written
- by Kenneth Yarnall. They may be freely distributed.
-
- TurboText is a trademark of Oxxi, Inc..
- SAS/C is a trademark of SAS Institute.
- ---------------------------------------------------------------------
-
- Table of Contents
- -----------------
-
- I. Installation
- II. Using the menus
- III. Other keys
- IV. SetDefs.ttx
- V. Changes
-
-
- I. Installation
- ---------------
-
- 1) Place the supplied files as follows:
-
- o Move the contents of the Rexx drawer to the REXX: directory on your
- system.
-
- o Move the contents of the Support drawer to the directory
- TURBOTEXT:Support/.
-
- o Move the file ENV/SC/SCMSG to ENVARC:SC/ *AND* to ENV:SC/.
-
- 2) To install the SASC menus under TurboText, do one of the following.
-
- o Choose Prefs/Open Defs... (Right-Amiga-/ in the standard TurboText
- setup) and select TTX_SASC.dfn in the file requester. The two menus
- that control the SAS/C 6.0 compiler should appear in TurboText's menu
- strip.
-
- o To make this a permanent addition to your system, insert the lines
-
- LINKS:
- TURBOTEXT:Support/TTX_SASC.dfn
-
- to your Startup.dfn file. Alternately, you can merge the contents of
- TTX_SASC.dfn with Startup.dfn, or see the section below on
- SetDefs.ttx.
-
- 3) To use the message browser, remember that you must set the "ErrorRexx"
- option of the SAS/C compiler.
-
- ---------------------------------------------------------------------
-
- II. Using the menus
- -------------------
-
- SAS/C
-
- Make Project... F6
- This entry starts SCmsg if it isn't running, and issues a build
- command in the directory of the file currently being edited. SMake
- will be run in that directory, and if you have the "ErrorRexx" option
- set for the compiler, warnings and errors will appear in the message
- browser.
-
- Compile File... ^F6 (Control F6)
- This compiles the file in the current TurboText window. SC is called
- directly; SMake is not used.
-
- Set Options... F7
- Calls up SCOptions, first changing to the directory of the document
- in the current TurboText window. This allows you to set the compiler
- options that will be used for the source file you are editing.
-
- Debug Program ยป
- CLI
- WB
- These allow you to execute CodeProbe on the executable associated
- with the document in the current TurboText window. Choose CLI to
- have the program started in a CLI environment, WB to have it started
- from the Workbench. The assumption made is that the program is in the
- same directory as the file being edited, and is named similarly,
- minus a ".c" suffix. For instance, if you are editing
- Work:MySource/Foo.c, this menu option will try to debug the program
- Work:MySource/Foo. Note that if there is no such program, CPR exits
- harmlessly.
-
- SCmsg
-
- Show Browser
- Hide Browser
- Clear Browser
- These show the SCmsg message browser window, hide it, and clear of of
- all messages, respectively. They do not try to start SCmsg if it is
- not running, and instead exit with an error.
-
- Current F8
- Previous F9
- Next F10
- First
- Last
- These navigate amongst the messages shown in the message browser's
- window, using the macro ErrorStep.ttx. They move the TurboText
- cursor to the line indicated in the current, previous, next, first,
- or last message, respectively. If the error occurs in a source file
- not currently loaded into a TurboText window, you are asked if you
- want to load that file.
-
- Delete
- Deletes the currently highlighted message from the browser's window.
-
- ---------------------------------------------------------------------
-
- III. Other keys
- ---------------
-
- CTRL-HELP
- FunctionHelp.ttx is attached to this key by the supplied dfn
- file. Press that key while the cursor is over the name of a
- standard library function name, and the SAS/C AmigaGuide help
- system is invoked.
-
- ALT-C
- The supplied dfn file (TTX_SASC.dfn) also attaches CommentBlk.ttx
- to the key ALT-C. This macro is supplied with TTX, and I found it
- handy.
-
- ---------------------------------------------------------------------
-
- IV. SetDefs.ttx
- ----------------
-
- SetDefs.ttx is a little macro I whipped up some time ago that I thought
- I'd include here. It is a "Poor Man's DataTypes"; it checks the extension
- of the file that you're loading, and opens an appropriate definitions file.
- The supplied version understands .c, .h, .cpp, .cxx, and .tex (you may want
- to change the last one, depending on your system).
-
- Any ARexx-aware programmer can glance at the script and see how to extend
- it to cover other extensions. Note that the macro is slightly smart, in
- that it doesn't load a new def's file unless it thinks it needs to.
-
- To install SetDefs.ttx, drop it in REXX: and then modify the file
- TTX_Startup.dfn to contain the lines (in the MENU " Project " section):
-
- ITEM "Open..." "O" ExecArexxString "OpenFile; Call 'rexx:SetDefs.ttx'"
-
- ITEM "Open New..." "Y"
- ExecArexxString "OpenDoc FileReq MACRO 'rexx:SetDefs.ttx'"
-
- (the last is all one line, albeit a long one). This patches the open
- functions inside TTX so that the extensions are obeyed. I also have
-
- ALT-D ExecArexxString "SetClip('extension',''); Call 'Rexx:SetDefs.ttx'"
-
- in the keyboard section, so that I can hit ALT-d to load the proper defs for
- the current file.
-
- Using SetDefs.ttx means that you don't have to Link TTX_SASC.dfn into your
- startup dfn file, as I outlined in the instructions above. This keeps
- things a bit cleaner, I think.
-
- I find myself using this all the time. When/if TTX windows become
- independent, such a macro can be much more powerful.
-
- ---------------------------------------------------------------------
-
- V. Changes
- ----------
-
- 2.1
- ---
- Cleaned up the code a bit (took a suggestion from Richard O'Sullivan and
- mod'ed out the common code into a few external routines). Fixed a couple of
- multitasking holes in Middleman.rexx.
-
- Added support for public screens. SCOpts, SCMsg, and the console window
- that Compile.ttx opens all now follow TTX onto whatever public screen TTX is
- currently inhabiting. SCMsg will actually hop around to follow TTX, so you
- can get them in a game of chase, if you like. :-)
-
- 2.0 (not a general release)
- ---
- Extensive rewrite of the scripts. Added Middleman.ttx, so that clicking
- on the entries in the SCmsg window works. Added some code to Build.ttx and
- Compile.ttx to check the state of the file you're working on, and ask if you
- want to save, etc., if it's needed. Added some comments and generally
- cleaned. Included SetDefs.ttx and FunctionHelp.ttx.
-
- 1.1
- ---
- Initial Public Release.
-
- ---------------------------------------------------------------------
-
- That is it!
-
- You may send questions/comments/improvements/bug reports to the author on
- BIX (kyarnall), and via internet mail at kyarnall@BIX.com.
-