head	1.6;
access;
symbols
	RELEASE_8_3_0:1.6
	RELEASE_9_0_0:1.6
	RELEASE_7_4_0:1.5
	RELEASE_8_2_0:1.5
	RELEASE_6_EOL:1.5
	RELEASE_8_1_0:1.5
	RELEASE_7_3_0:1.5
	RELEASE_8_0_0:1.5
	RELEASE_7_2_0:1.5
	RELEASE_7_1_0:1.5
	RELEASE_6_4_0:1.5
	RELEASE_5_EOL:1.5
	RELEASE_7_0_0:1.5
	RELEASE_6_3_0:1.5
	PRE_XORG_7:1.5
	RELEASE_4_EOL:1.5
	RELEASE_6_2_0:1.5
	RELEASE_6_1_0:1.5
	RELEASE_5_5_0:1.5
	RELEASE_6_0_0:1.5
	RELEASE_5_4_0:1.5
	RELEASE_4_11_0:1.5
	RELEASE_5_3_0:1.5
	RELEASE_4_10_0:1.5
	RELEASE_5_2_1:1.5
	RELEASE_5_2_0:1.5
	RELEASE_4_9_0:1.5
	RELEASE_5_1_0:1.5
	RELEASE_4_8_0:1.5
	RELEASE_5_0_0:1.5
	RELEASE_4_7_0:1.5
	RELEASE_4_6_2:1.5
	RELEASE_4_6_1:1.5
	RELEASE_4_6_0:1.5
	RELEASE_5_0_DP1:1.5
	RELEASE_4_5_0:1.5
	RELEASE_4_4_0:1.4
	RELEASE_4_3_0:1.4
	RELEASE_4_2_0:1.4
	RELEASE_4_1_1:1.3
	RELEASE_4_1_0:1.3
	RELEASE_3_5_0:1.3
	RELEASE_4_0_0:1.2
	RELEASE_3_4_0:1.2
	RELEASE_3_3_0:1.2
	RELEASE_3_2_0:1.2
	RELEASE_3_1_0:1.2
	RELEASE_2_2_8:1.2
	RELEASE_3_0_0:1.2
	RELEASE_2_2_7:1.2
	RELEASE_2_2_6:1.1.1.1
	RELEASE_2_2_5:1.1.1.1
	RELEASE_2_2_1:1.1.1.1
	RELEASE_2_2_2:1.1.1.1
	rexximc_1_6d:1.1.1.1
	IMC:1.1.1;
locks; strict;
comment	@# @;


1.6
date	2011.10.24.09.10.14;	author dougb;	state Exp;
branches;
next	1.5;

1.5
date	2001.09.22.20.13.15;	author lioux;	state Exp;
branches;
next	1.4;

1.4
date	2000.10.28.15.57.59;	author kevlo;	state Exp;
branches;
next	1.3;

1.3
date	2000.05.29.02.20.47;	author steve;	state Exp;
branches;
next	1.2;

1.2
date	98.05.03.18.03.34;	author steve;	state Exp;
branches;
next	1.1;

1.1
date	96.09.23.15.50.10;	author jfitz;	state Exp;
branches
	1.1.1.1;
next	;

1.1.1.1
date	96.09.23.15.50.10;	author jfitz;	state Exp;
branches;
next	;


desc
@@


1.6
log
@The vast majority of pkg-descr files had the following format when they
had both lines:

Author: ...
WWW: ....

So standardize on that, and move them to the end of the file when necessary.

Also fix some more whitespace, and remove more "signature tags" of varying
forms, like -- name, etc.

s/AUTHOR/Author/

A few other various formatting issues
@
text
@REXX/imc is a Rexx interpreter for Unix. It supports all the standard 
instructions and built-in functions, plus a small number of extensions, 
and has a partial implementation of the SAA API allowing applications 
to call Rexx programs and to register addressing environments, Rexx 
functions, and exit handlers. 

WWW: http://users.comlab.ox.ac.uk/ian.collier/Rexx/rexximc.html
@


1.5
log
@o update to 1.75
o support NOPORTDOCS
o assign maintainership to submitter

PR:		30428
Submitted by:	John Merryweather Cooper <jmcoopr@@webmail.bmi.net>
@
text
@a7 3

--
John Merryweather Cooper <jmcoopr@@webmail.bmi.net>
@


1.4
log
@Update MASTER_SITES and WWW: line of pkg-descr

PR: 22366
Submitted by: Ports Fury
@
text
@d8 3
@


1.3
log
@- Support CFLAGS properly
- Fix procedure of building shared library
- Sort pkg/PLIST
- Revise pkg/DESCR

PR:		18797
Submitted by:	KATO Tsuguru <tkato@@prontomail.ne.jp>
@
text
@d7 1
a7 1
WWW: http://www.comlab.ox.ac.uk/oucl/users/ian.collier/Rexx/index.html
@


1.2
log
@Install rexxsaa.h and portlint clean.

PR:		6478
Submitted by:	Pedro Giffuni <giffunip@@asme.org>
@
text
@d1 5
a5 2
What is REXX ?
==============
d7 1
a7 61
REXX is a programming language designed by Michael Cowlishaw
of IBM UK Laboratories.  In his own words:  "REXX is a
procedural language that allows programs and algorithms to
be written in a clear and structured way."
REXX doesn't look that different from any other procedural
language.  Here's a simple REXX program:

     /* Count some numbers */
     
     say "Counting..."
     do i = 1 to 10
         say "Number" i
     end

What makes REXX different from most other languages is that
it is also designed to be used as a macro language by
arbitrary application programs.  The idea is that
application developers don't have to design their own macro
languages and interpreters.  Instead they use REXX as the
macro language and support the REXX programming interface.
If a REXX macro comes across an expression or function call
that it cannot resolve, it can ask the application to handle
it instead.  The application only has to support the
features that are specific to it, freeing the developer from
handling the mundane (and time-consuming) task of writing a
language interpreter.  And if all applications use REXX as
their macro language, the user only has to learn one
language instead of a dozen.


Differences between TRL (The REXX Language) and REXX/imc
========================================================

The following are all nonstandard features of REXX-imc

 * Rejection of labels ending with dot (in case of confusion between
   function.(args) and stem.(tail))
 * Compound variable accesses of the form "stem.'string constant'" and
   stem.(expression)
 * Acceptance of any non-zero number for logical truth, rather than just 1
 * "SAYN expression" to output lines without carriage return
 * "SELECT expression" to switch on a value
 * "END SELECT"
 * "PARSE VALUE" with multiple strings separated by commas
 * "PROCEDURE HIDE"
 * The following functions: chdir getcwd getenv putenv system userid
   plus these I/O functions: open close fdopen popen pclose fileno ftell
 * error messages 80-210, -1 and -3.


Good sources of REXX information on the web:
============================================

REXX/imc Home page
	http://www.comlab.ox.ac.uk/oucl/users/ian.collier/Rexx/index.html

IBM's REXX Language Page
	http://rexx.hursley.ibm.com/rexx/

REXX Tutorials Page
	http://www2.hursley.ibm.com/rexxtut/
@


1.1
log
@Initial revision
@
text
@a64 1

@


1.1.1.1
log
@Import of REXX/imc, a REXX interpreter for unix.
Reviewed by:	matt@@bdd.net
@
text
@@
