Value range tracing

deaeni@auto-trol.com (Dean Enix)
9 Dec 1995 19:41:34 -0500

          From comp.compilers
Related articles
[2 earlier articles]
Re: Value range tracing hbaker@netcom.com (1995-12-09)
Re: Value range tracing preston@tera.com (1995-12-09)
Re: Value range tracing schinz@guano.alphanet.ch (1995-12-09)
Value range tracing dave@occl-cam.demon.co.uk (Dave Lloyd) (1995-12-09)
Re: Value range tracing bernecky@eecg.toronto.edu (1995-12-09)
Re: Value range tracing creusil@cri.ensmp.fr (1995-12-09)
Value range tracing deaeni@auto-trol.com (1995-12-09)
Re: Value range tracing gough@dstc.qut.edu.au (John Gough) (1995-12-09)
Re: Value range tracing jason@reflections.com.au (Jason Patterson) (1995-12-09)
Re: Value range tracing bill@amber.ssd.hcsc.com (1995-12-09)
Re: Value range tracing vadik@cs.umd.edu (1995-12-17)
Re: Value range tracing mab@wdl.loral.com (1995-12-17)
| List of all articles for this month |
From: deaeni@auto-trol.com (Dean Enix)
Newsgroups: comp.compilers
Date: 9 Dec 1995 19:41:34 -0500
Organization: Compilers Central
References: 95-12-014
Keywords: analysis, optimize

We use domain checking as part of our UI component. It assures the
application obtains valid values and alerts the user at the soonest
possible moment of out of range values.


We have implemented this for common data types and extended data types
such as dates...


We support both range checking & one of a list of ennumerated values.


Additionally we have database calls from the ui that allow us to
check if a value already exists or does not exist...


The application has an API to modify domain checking on the fly, so
that if domains change the UI is appraised of it.


Dean
--

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.