summaryrefslogtreecommitdiff
path: root/lang/sather
AgeCommit message (Collapse)AuthorFilesLines
2003-04-29Fix use of _OPSYS_RPATH_NAME causing broken compiler.jtb7-55/+47
Bump PKG_REVISION.
2003-03-10Needs -Wl,-R (or the equiv) when linking libgc. Pass _OPSYS_RPATH_NAME in ↵jmc4-8/+9
and use that accordingly.
2002-09-23buildlink1 -> buildlink2jlam1-15/+20
2002-05-09Don't bother using EVAL_PREFIX to find the prefices of boehm-gc, tclagc1-17/+9
or tk, since they are all installed into ${LOCALBASE}. Weakly buildlink-ify this package. When installing, install the files from ${WRKSRC} into ${PREFIX} and then change the ownership, rather than doing it the other way around. This allows non-root users to "make clean" in the package directory.
2002-05-04Initial import of sather.jtb27-0/+960
Sather is an object oriented language which designed to be simple, efficient, safe, and non-proprietary. It aims to meet the needs of modern research groups and to foster the development of a large, freely available, high-quality library of efficient well-written classes for a wide variety of computational tasks. It was originally based on Eiffel but now incorporates ideas and approaches from several languages. One way of placing it in the "space of languages" is to say that it attempts to be as efficient as C, C++, or Fortran, as elegant and safe as Eiffel or CLU, and to support higher-order functions as well as Common Lisp, Scheme, or Smalltalk. Sather has garbage collection, statically-checked strong typing, multiple inheritance, separate implementation and type inheritance, parameterized classes, dynamic dispatch, iteration abstraction, higher-order routines and iters, exception handling, assertions, preconditions, postconditions, and class invariants. Sather code can be compiled into C code and can efficiently link with C object files.