Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site water.UUCP
Path: utzoo!watmath!watnot!water!ylfink
From: ylfink@water.UUCP (ylfink)
Newsgroups: ont.events
Subject: UW CS Colloq. Semi., Prof. Buhr on "A Programming Environment for a Strongly      and Statically Typed Programming Language".
Message-ID: <206@water.UUCP>
Date: Tue, 11-Feb-86 13:28:42 EST
Article-I.D.: water.206
Posted: Tue Feb 11 13:28:42 1986
Date-Received: Wed, 12-Feb-86 20:20:09 EST
Expires: Fri, 14-Feb-86 00:00:00 EST
Organization: U of Waterloo, Ontario
Lines: 43


DEPARTMENT OF COMPUTER SCIENCE
UNIVERSITY OF WATERLOO
SEMINAR ACTIVITIES

COMPUTER SCIENCE COLLOQUIUM

                    - Thursday, February 13, 1986.

Professor Peter Buhr of the University of Manitoba will
speak on ``A Programming Environment for a Strongly and
Statically typed Programming Language''.

TIME:                3:30 PM

ROOM:              MC 3003

ABSTRACT

Designing  a programming environment for a strongly and
statically  typed  programming language (SSTPL) is more
complex than for a non-typed (e.g. LISP, APL) or dynam-
ically  typed  (Smalltalk,  ML)  programming  language.
While  there  will be similarities in facilities a pro-
gramming  environment might provide for both classes of
programming  languages, the former has the added burden
of  guaranteeing  type-safety statically.  Conventional
systems  for a SSTPL usually guarantees type-safety for
only  a single monolithic program.  References to other
separately compiled programs or external files are usu-
ally not type checked.  This failure of the programming
environment to guarantee type-safety for all references
to  all  entities  severely  undermines the fundamental
purpose of data-typing in a SSTPL.

This  talk will argue against the development of a com-
plex  programming environment (e.g. ASPE) to solve this
problem.   Instead, with appropriate augmentation, much
of  what  is  traditionally  thought of as programming-
environment  function  can  be embedded in a SSTPL, and
this  language  can  then be used directly to provide a
powerful coherent type-safe system for program develop-
ment, testing and subsequent usage by end-users.