@database E_Bed Scripts
@node "Main" "Bed Scripts for Amiga E"

      3 ARexx Scripts for BED to run Amiga E v2.1b

@{"Read This!!!  " LINK "Read"}  Important information.
@{"introduction  " LINK "intro"}
@{"Requirements  " LINK "Requirements"}
@{"Installation  " LINK "Installation"}
@{"How to use    " LINK "Usage"}
@{"Author        " LINK "Me"}
@{"History       " LINK "History"}
@{"Known Bugs    " LINK "bugs"}
@endnode
@node "Read" "Copyright Information"

                             IMPORTANT
                             ---------
 ---------------------------------------------------------------------------
 This software is subject to the "Standard Amiga FD-Software Copyright Note".
 It is E-Mailware as defined in paragraph 4<b>.
 For more information please read "AFD-COPYRIGHT" (Version 1 or higher).
 ---------------------------------------------------------------------------


@endnode
@node "intro" "Introduction"
This is a set of ARexx Macros to run the E 2.1b Complier from within BED.
These were written by me a couple of years ago, for my own use. The release
of a new version of BED has prompted me to release these to the Amiga
community.

These scripts have been written for E 2.1b but they might work with other
versions - I'd like to hear if they do (or don't)

@endnode
@node "Requirements" "What's required"
Requires: An Amiga (With ARexx running)
          BED
          Amiga E v2.1b - Installed correctly
          reqtools.library and rexxreqtools.library
          if you wish to be able to supply arguments to your programs
          
@endnode
@node "Installation" "How to Install"
Sorry, but there is no installer script yet, however manual installation is
not too hard.
Copy the drawer 'E' into the Bed/Rexx drawer
Copy E.dfn to Bed/support

Note: I have NOT included either an E.prf or a File_Startup.bed script
because these tend to be set according to personal tastes. I feel it is best
for you to provide your own.

You'll need to add something like this to your File_startup.bed

		WHEN (ext = 'e') THEN DO
			OpenPrefs "BED:Support/E.prf"
			OpenDefinitions "BED:Support/E.dfn"
		END



@endnode
@node "Usage"
If you have installed these files correctly, when you load an E source code
into Bed, a new 'E' menu with 3 items in it will appear.

Compile: invokes the EC compiler. EC requires a file stored on disk, so the
file you are editing will be saved if it has been changed.
Hopefully every thing will be OK in which case 'Compiled Succesfully' will be
displayed in the statusbar.
If any errors are detected during compilation a suitable error message will
appear in the statusbar, and the cursor will be moved to the offending line.
For some errors you will also be moved to the part of the line at fault.

If unreferenced variables are found 'URF: ' with a list of them will be
displayed at the end of the statusbar message. (This might not be visible
with long error messages)

Run...:  opens a string requester for you to enter a command line, then runs
a previously compiled program.

Run: runs the compiled program without prompting for arguments.

@endnode
@node "Me" "Author Info"

Author : Darren Stevens
         19 Minton Street,
         Clough Road
         Hull,
         HU5 1QP
         
         E-Mail: daz@sunhawk.u-net.com
         
@endnode
@node "History"
1.3 17/03/98 Opps! Found I wasn't dealing with unreferenced variables at
all! Took the oppertunity to clean up the code a little.

1.2 10/03/98 Found and removed (hopefully) a small problem with E sources
ending with numbers e.g. test2.e - EC was outputting different control codes
in its output, causing Complie.bed to fail. Finally finished adding reqtools
support in RunA.bed - can now run programs with a command line.

1.1 11/11/97 Added better error checking in Complie.Bed - now checks for
non-existent files/not E-source codes.

1.0 28/09/96 First version. For my use only. Not released.

@endnode
@node "bugs"
Most of the time you should not have any trouble, but there are some things
I have not dealt with. (Yet) The warnings spring to mind, As I havn't
encountered these yet, I don't know what effect they will have on the scripts.

Lines seperated with a ',' are treated as one line, if the error is in the
second (or third line etc..) you will sometimes be placed at the beginning
of the first line.

The is also likely to be a problem with the ':= expected' error due to it
having a ':' in.

There are probably other bugs too. If you find one let me know.
@endnode