Re: Bird 35

Text item:

I like this suggestion.
Arpad

2) I think that a much easier way of organizing this data would be for the
new construct to refer to existing device models (that already have their own
pull-ups and VT arrays) and then just specify their relative scheduling.

Text item: External Message Header

The following mail header is for administrative use
and may be ignored unless there are problems.

***IF THERE ARE PROBLEMS SAVE THESE HEADERS***.

Subject: Bird 35
Cc: jonp@qdt.com, bob@icx.com
To: ibis@vhdl.org
Received: by f14.qdt.com (4.1/SMI-4.1)
     id AA19338; Wed, 12 Jun 96 11:16:24 PDT
Message-Id: <9606121816.AA02610@hal.qdt.com>
From: jonp@qdt.com (Jon Powell)
Date: Wed, 12 Jun 96 11:16:26 PDT
Received: from f14.qdt.com by hal.qdt.com (4.1/SMI-4.1)
     id AA02610; Wed, 12 Jun 96 11:16:26 PDT
Received: from hal.qdt.com by qdt.com (4.1/SMI-4.1)
     id AA00863; Wed, 12 Jun 96 11:16:25 PDT
Received: from qdt.UUCP by uucp6.UU.NET with UUCP/RMAIL
        ; Wed, 12 Jun 1996 15:02:14 -0400
Received: from uucp6.UU.NET by relay5.UU.NET with SMTP
     (peer crosschecked as: uucp6.UU.NET [192.48.96.37])
     id QQatuy10177; Wed, 12 Jun 1996 15:02:14 -0400 (EDT)
Received: from relay5.UU.NET (relay5.UU.NET [192.48.96.15]) by vhdl.vhdl.org (8.
7.3/8.7.3) with ESMTP id MAA21990 for <ibis@vhdl.org>; Wed, 12 Jun 1996 12:11:51
 -0700 (PDT)
Received: from vhdl.vhdl.org (vhdl.vhdl.org [198.31.14.3]) by ormail.intel.com (
8.7.4/8.7.3) with ESMTP id MAA19870; Wed, 12 Jun 1996 12:05:00 -0700 (PDT)
Received: from ormail.intel.com (ormail.intel.com [134.134.248.3]) by relay.jf.i
ntel.com (8.7.4/8.7.3) with ESMTP id MAA11263; Wed, 12 Jun 1996 12:04:58 -0700 (
PDT)
Return-Path: owner-ibis@vhdl.vhdl.org
Received on Thu Jun 13 11:34:33 1996