head	1.6;
access;
symbols
	RELEASE_8_3_0:1.6
	RELEASE_9_0_0:1.6
	RELEASE_7_4_0:1.6
	RELEASE_8_2_0:1.6
	RELEASE_6_EOL:1.6
	RELEASE_8_1_0:1.6
	RELEASE_7_3_0:1.6
	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.5
	RELEASE_4_3_0:1.5
	RELEASE_4_2_0:1.5
	RELEASE_4_1_1:1.5
	RELEASE_4_1_0:1.5
	RELEASE_3_5_0:1.5
	RELEASE_4_0_0:1.5
	RELEASE_3_4_0:1.5
	RELEASE_3_3_0:1.5
	RELEASE_3_2_0:1.5
	RELEASE_3_1_0:1.4
	RELEASE_2_2_8:1.4
	RELEASE_3_0_0:1.4
	RELEASE_2_2_7:1.4
	RELEASE_2_2_6:1.4
	RELEASE_2_2_5:1.3
	RELEASE_2_2_1:1.3
	RELEASE_2_2_2:1.3
	icon9_0:1.1.1.1
	icon:1.1.1;
locks; strict;
comment	@# @;


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

1.5
date	99.05.03.06.13.06;	author mharo;	state Exp;
branches;
next	1.4;

1.4
date	98.02.20.12.19.48;	author tg;	state Exp;
branches;
next	1.3;

1.3
date	96.11.05.08.34.04;	author tg;	state Exp;
branches;
next	1.2;

1.2
date	95.07.29.09.55.11;	author asami;	state Exp;
branches;
next	1.1;

1.1
date	95.04.06.08.52.44;	author jkh;	state Exp;
branches
	1.1.1.1;
next	;

1.1.1.1
date	95.04.06.08.52.44;	author jkh;	state Exp;
branches;
next	;


desc
@@


1.6
log
@For ports maintained by ports@@FreeBSD.org, remove names and/or
e-mail addresses from the pkg-descr file that could reasonably
be mistaken for maintainer contact information in order to avoid
confusion on the part of users looking for support. As a pleasant
side effect this also avoids confusion and/or frustration for people
who are no longer maintaining those ports.
@
text
@   Icon is a high-level programming language with extensive facilities for
processing strings and structures.  Icon has several novel features,
including expressions that may produce sequences of results, goal-directed
evaluation that automatically searches for a successful result, and string
scanning that allows operations on strings to be formulated at a high
conceptual level.

The language is described in R.  E.  Griswold and M.  T.  Griswold, The
Icon Programming Language, Prentice-Hall, Inc., Englewood Cliffs, NJ,
second edition, 1990.

For more information or assistance, contact:

Icon Project                             voice: (520) 621-6613
Department of Computer Science	         fax:   (520) 621-4246
The University of Arizona
P.O. Box 210077                          icon-project@@cs.arizona.edu    
Tucson, AZ   85721-0077			                                        
U.S.A.					 

WWW: http://www.cs.arizona.edu/icon/
@


1.5
log
@Yet more WWW: additions
@
text
@d20 1
@


1.4
log
@Upgrade to 9.3.1.
@
text
@d19 2
a20 1
U.S.A.					 http://www.cs.arizona.edu/icon/
@


1.3
log
@Upgrade to version 9.1
@
text
@d1 6
a6 7
   Icon is a high-level programming language with extensive
facilities for processing strings and structures. Icon has
several novel features, including expressions that may produce
sequences of results, goal-directed evaluation that automatically
searches for a successful result, and string scanning that allows
operations on strings to be formulated at a high conceptual
level.
d8 3
a10 15
   Icon emphasizes high-level string processing and a design phi-
losophy that allows ease of programming and short, concise pro-
grams. Storage allocation and garbage collection are automatic in
Icon, and there are few restrictions on the sizes of objects.
Strings, lists, and other structures are created during program
execution and their size does not need to be known when a program
is written.  Values are converted to expected types automati-
cally; for example, numeral strings read in as input can be used
in numerical computations without explicit conversion.  Icon has
an expression-based syntax with reserved words; in appearance,
Icon programs resemble those of Pascal and C.

The language is described in R. E. Griswold and M. T. Griswold, The
Icon Programming Language, Prentice-Hall, Inc., Englewood Cliffs,
NJ, second edition, 1990.
d12 1
d14 6
@


1.2
log
@Install machine-independent scripts into /usr/local/share, etc.

Submitted by:	Thomas Gellekum <thomas@@ghpc8.ihf.rwth-aachen.de>
@
text
@a24 2
For further documentation see the docs directory in the
unpacked source tree (make extract; cd work/docs).
@


1.1
log
@Initial revision
@
text
@d21 7
@


1.1.1.1
log
@The Icon Programming Language, version 9.0
Submitted by:	Thomas Gellekum <thomas@@ghpc8.ihf.rwth-aachen.de>
@
text
@@
