HDTenEightyP/NetNews huggingface dataset:
From: landsman@stars.gsfc.nasa.gov (Wayne Landsman (301)-286-3625)
Subject: /NORM with OPLOT and other thoughts
News-Software: VAX/VMS VNEWS 1.4-b1  
Organization: NASA/GSFC-Laboratory for Astronomy and Solar Physics
Date: Sun, 16 Aug 1992 21:07:00 GMT


     I am trying to write the annotation on a plot, which explains the
meaning of each of the PSYM symbols I used.    When writing annotation
I like to use normalized coordinates.   But, as far as I can tell, the
/NORMAL (and /DEVICE) keywords are ignored by OPLOT.    For example,

     IDL> x = indgen(10)   &   y = indgen(10)
     IDL> plot, x, y
     IDL> oplot, [0.5], [0.7], PSYM =4, /NORM

      and the coordinates (0.5,0.7) are treated like data coordinates despite
the /NORM keyword.    (As an aside, it would also be nice if OPLOT accepted 
scalars, so that one wouldn't have to convert the scalars to 1 element
vectors.)      Of course, I can use the CONVERT_COORD procedure to get
the "true" data coordinates

     IDL> xx = convert_coord( 0.5, 0.7, /NORM, /TO_DATA)
     IDL> oplot, [xx(0)], [ yy(0) ], PSYM = 4 

but this seems like an unnecessary complication.

      What would be really nice would be if I could write the PSYM characters
with XYOUTS, so that I could write my annotation with a single line.   I can
do this with some of the PSYM characters (e.g. the plus sign PSYM = 1)

      IDL> xyouts, 0.5, 0.7, '(+) Model 1', /NORM

but, for example, the diamond (PSYM=4) cannot be written with XYOUTS.

Wayne Landsman
landsman@stars.gsfc.nasa.gov
Newsgroups: comp.lang.idl-pvwave
From: thompson@stars.gsfc.nasa.gov (William Thompson, code 682.1, x2040)
Subject: Re: IDL User's Library routine ROT
News-Software: VAX/VMS VNEWS 1.4-b1  
Organization: NASA/GSFC-Laboratory for Astronomy and Solar Physics
Date: Thu, 13 Aug 1992 14:29:00 GMT

In article <12AUG199218251536@stars.gsfc.nasa.gov>, fireman@stars.gsfc.nasa.gov
(Gwyn Fireman) writes...
>	Hello, IDL users -
> 
>	I've been trying to figure out the IDL User's Library routine ROT, and
>am now pretty confused.  It seems to me that a 90-degree rotation should have
>the same result for both ROT and the built-in function ROTATE, at least for
>square matrices, and that interpolation shuld have no effect.  This is not the
>case.  Even or odd array sizes make no difference.  Am I missing something
>obvious?  Is there a better routine for doing array rotations in non-multiples
>of 90 degrees?

(rest of message deleted)

The problem seems to be one of integer truncation.  ROT uses "nearest neighbor"
interpolation.  In other words, it tries to find the nearest pixel to where it
calculates the rotated pixel to be.  When the rotation angle is 90 degrees,
that should give an exact solution.  However, roundoff errors in the
calculation may calculate the nearest pixel as, say, 4.0001,5.9999 when it
should be 4,6.  The 4.0001 is no problem since it be truncated correctly to 4.
The 5.9999, however, will be truncated incorrectly to 5.  Thus, there will be
one pixel shifts in various parts of the image.

Maybe ROT could be rewritten to avoid these integer truncations.  Another work
around is to use ROT_INT instead of ROT.  Since this does bilinear
interpolation, it's not sensitive to this integer truncation problem.  It also
gives a better looking rotated picture.  There may be slight changes in the
values, particularly for integer arrays (a different truncation effect).  There
are also some funny effects at the corners, which is unavoidable.

Bill Thompson
Newsgroups: comp.lang.idl-pvwave
From: fedor@csn.org (Adam Fedor)
Newsgroups: comp.lang.idl-pvwave
Subject: Re: PVI jerk toots own horn on net [flame; how'd you guess? :-]
Date: 20 Aug 92 17:59:45 GMT
Organization: University of Colorado, Boulder

In article <ALANS.92Aug19170731@abraham.juliet.ll.mit.edu> alans@ll.mit.edu (Alan Jay Stein) writes:
>As you may recall, On Wed, 19 Aug 1992 16:30:13 GMT, greg@pvi.UUCP (Greg Holling x376) said:
>

[lots of flamable personal attacks and suspected advertisments deleted]
>
>First of all, this is no place to advertise! I can't believe PVI doesn't have a
>corporate policy prohibiting this, but I'm sure gonna find out now! 
>

I ain't saying whether IDL or PV-WAVE is better, but even if Greg's comment
was an advertisment (which is debatable), I think personal attacks on someone's
character are far more reprehensible. Lets try to discuss
matters of etiquette (via e-mail hopefully) rationally, since the difference
between commencial and non-commercial use of the net is often a very fine
line (see comp.newprod, comp.sys.next.announce, and probably a few others).


-- 
Adam Fedor. CU, Boulder		| Fudd's Law of Opposition: Push something  
fedor@boulder.colorado.edu 	|   hard enough and it will fall over. 
Newsgroups: comp.lang.idl-pvwave
From: snoopy@unlv.edu (Ramesh Viswanathan)
Subject: Re: /NORM with OPLOT and other thoughts
Organization: UNLV
Date: Tue, 18 Aug 92 18:08:25 GMT

In article <16AUG199217070886@stars.gsfc.nasa.gov> landsman@stars.gsfc.nasa.gov (Wayne Landsman (301)-286-3625) writes:

>with XYOUTS, so that I could write my annotation with a single line.   I can
>do this with some of the PSYM characters (e.g. the plus sign PSYM = 1)

>      IDL> xyouts, 0.5, 0.7, '(+) Model 1', /NORM

>but, for example, the diamond (PSYM=4) cannot be written with XYOUTS.


Have you tried using the symbol character set (Font 9, Math and
Special) with the xyouts procedure?  I think the letter V maps
to a diamond symbol in this character set.  The xyouts command
line could then look somethink like:

	IDL> xyouts, 0.5, 0.7, '(!9V!3) Model 1', /NORM

Where the !9 shits output character set to Math and Special, and
since V is mapped to a diamond, a diamond symbol is drawn. Subse-
quently, the !3 changes the output character set back to Simplex
Roman font (which is the default). The output will appear as your
example above, but the + sybol will instead be replace by a dia-
mond.


-rv 
(email: ercrav@vegas1.las.epa.gov)
Newsgroups: comp.lang.idl-pvwave
From: snoopy@unlv.edu (Ramesh Viswanathan)
Subject: Re: Color table question
Organization: UNLV
Date: Fri, 14 Aug 92 21:38:36 GMT


If, after trying all the previous suggestions, the image still
doesn't improve the problem may lie in the distribution of the
data across the dynamic range of the display system.  This can
be improved by normalizing the data-set so that the frequency
distribution (histogram) or the pdf (probability density
function) of the data will be flat across the entire range of
the data or the display system.

You can do a histogram equalization (or normalization) on the
data with the following command:

	newdata = HIST_EQUAL(olddata)

and then redisplay the modified data.


Although this will improve the dynamic range of the data itself,
the result still depends somewhat upon the choice of the color-
table.

--rv


P.S.

Also, in the original posting where the data was scaled to fit
into bytes (using BYTSCL) and values less than 10 were zeroed
out, the following version of BYTSCL using keywords min and max
may be used instead with perhaps better results:

	newdata = BYTSCL(olddata, min=10, max=max(olddata))
From: fireman@stars.gsfc.nasa.gov (Gwyn Fireman)
Subject: IDL User's Library routine ROT
News-Software: VAX/VMS VNEWS 1.4-b1  
Organization: NASA/GSFC-Laboratory for Astronomy and Solar Physics
Date: Wed, 12 Aug 1992 22:25:00 GMT

	Hello, IDL users -

	I've been trying to figure out the IDL User's Library routine ROT, and
am now pretty confused.  It seems to me that a 90-degree rotation should have
the same result for both ROT and the built-in function ROTATE, at least for
square matrices, and that interpolation shuld have no effect.  This is not the
case.  Even or odd array sizes make no difference.  Am I missing something
obvious?  Is there a better routine for doing array rotations in non-multiples
of 90 degrees?

a=indgen(4,4)
print,a
;       0       1       2       3
;       4       5       6       7
;       8       9      10      11
;      12      13      14      15
print,rotate(a,1)
;      12       8       4       0
;      13       9       5       1
;      14      10       6       2	<-- so far, so good...
;      15      11       7       3
print,rot(a,90,missing=-1)		
;      -1       3       7      11
;      -1       2       6      10
;       1       5       9      13	<-- yuckadoo!
;       0       4       8      12
b=indgen(5,5)
print,b
;       0       1       2       3       4
;       5       6       7       8       9
;      10      11      12      13      14
;      15      16      17      18      19
;      20      21      22      23      24
print,rotate(b,1)
;      20      15      10       5       0
;      21      16      11       6       1
;      22      17      12       7       2
;      23      18      13       8       3
;      24      19      14       9       4
print,rot(b,90,missing=-1)
;      -1       3       8      13      18
;      -1       2       7      12      17
;      -1       1       6      12      17
;       0       5      10      15      21
;      -1      -1      -1      -1      20


 Gwyn Fireman                        phone:     (301) 794-1560            
 Computer Sciences Corporation       span:      IUEGTC::FIREMAN           
 IUE Observatory                     internet:  fireman@iuegtc.span.nasa.gov
From: bradleyt@spot.Colorado.EDU (Slan (rhymes with pawn))
Newsgroups: comp.lang.idl-pvwave
Subject: Re: PVI jerk toots own horn on net [flame; how'd you guess? : -]
Summary: who's calling the kettle black?
Date: 20 Aug 92 16:11:59 GMT
Organization: University of Colorado, Boulder

In article <ALANS.92Aug19170731@abraham.juliet.ll.mit.edu> alans@ll.mit.edu (Alan Jay Stein) writes:

[Several personal attacks not worthy of comment deleted...]

>***NOT!***
>
>First of all, this is no place to advertise! I can't believe PVI doesn't have a
>corporate policy prohibiting this, but I'm sure gonna find out now! 
>
>And about giving you some credit: 
>
>You charge way more for the same basic product, have no programmable X Widgets,
>and no IMSL link. And before you spout off about the NAG garbage, I'd like to
>remind you that this is a brain-dead, one for one parameter implementation, no
>easier than writing c-code which we can do without putting your kids through
>college. Apparantly, a few smart RSI engineers can do a lot more than a lot of
>stupid PV ones.
>
>And finally if you're working on a Unix box, can you really buy the "bigger 
>is better" argument? IDL wins on price, and on features. In conclusion,
>
>*************>  Stay Away from PVI, folks!!!  Buy IDL!!!  <****************

Geez, Al.  Stop beating around the bush and tell us what you really
think!  I mean, are you _for_ IDL or against it?

Todd.

-- 
| Todd Bradley -- Official Microsoft Spokesman
| 
| WARNING/GUARANTEE: This message contains material which a truly
| free Society would neither fear nor suppress.
From: gurman@umbra.gsfc.nasa.gov (Joseph B. Gurman)
Newsgroups: comp.lang.idl-pvwave
Subject: Re: PVI jerk toots own horn on net [flame; how'd you guess? : -]
Date: 22 Aug 92 03:00:08 GMT
Organization: Goddard Space Flight Center


    [Lots of harsh words from earlier posts; deep questions about the
relative merits of two very nifty software products; then the killer:]

>--
>Adam Fedor. CU, Boulder        | Fudd's Law of Opposition: Push
something
                                  ^^^^^^^^^^
>fedor@boulder.colorado.edu     |   hard enough and it will fall over.

    Surely you realize that this is Fudd's FIRST Law of Opposition. The
Second Law, as I recall, is something about wasting Usenet bandwidth
with flame wars in one of the few remaining useful newsgroups for people
trying to work. 'Nuff said?

P.S. This is not directed at you personally, Adam, nor anyone else, just
PLEASE let's cool this thing off: I learn quite a bit by reading this
newsgroup --- or did before Wednesday....

                                Joe Gurman

--
J.B. Gurman / Solar Physics Branch / NASA Goddard Space Flight Center /
Greenbelt MD 20771 USA / gurman@umbra.gsfc.nasa.gov
| Federal employees are prohibited from holding opinions under the Hatch Act.|
| Therefore, any opinions expressed herein are somebody else's.              |
From: sullivan@gorgo.gsfc.nasa.gov (Dan sullivan)
Newsgroups: comp.lang.idl-pvwave
Subject: IDL widget question
Date: 21 Aug 92 20:19:20 GMT
Reply-To: sullivan@gorgo.gsfc.nasa.gov (Dan sullivan)
Organization: NASA/GSFC Hydrospheric Sciences Branch


        Can anyone outline the widget calls to display a symmetric
2D table of buttons like the following ?
             -----------------
             | BB| |BB| | BB |
             ----  ---- ------
             |BBB| | B| |BBBB|
             -----------------
I want all buttons in a column to be the width of the widest button, and
all the buttons/labels/text widgets in a row to be equal height.
I can get the rows to align, or the columns to align, but I can't get
them both to align. (The button names are different lengths.) I get
something like :

             -----------------
             |BB| |B| |BB|
             ----  ---- ------
             |BBB| |B| |BBBB|
             -----------------

Thanks,  Dan
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dan Sullivan                   #  Laboratory for Terrestrial Physics (STX) 
                               #  Code 920.2
sullivan@gorgo.gsfc.nasa.gov   #  NASA-Goddard Space Flight Center
                               #  Greenbelt, MD 20771
                               #  voice: (301) 286-2484
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Newsgroups: comp.lang.idl-pvwave
From: toma@hyperion.gsfc.nasa.gov (Tom Atwater)
Subject: Re: /NORM with OPLOT and other thoughts
Organization: NASA Goddard Space Flight Center, Greenbelt, MD
Date: Mon, 17 Aug 1992 11:17:55 GMT

In article <16AUG199217070886@stars.gsfc.nasa.gov> landsman@stars.gsfc.nasa.gov (Wayne Landsman (301)-286-3625) writes:
>
>     I am trying to write the annotation on a plot, which explains the
>meaning of each of the PSYM symbols I used.    When writing annotation
>I like to use normalized coordinates.   But, as far as I can tell, the
>/NORMAL (and /DEVICE) keywords are ignored by OPLOT.

>      What would be really nice would be if I could write the PSYM characters
>with XYOUTS, so that I could write my annotation with a single line. 

I think that the PLOTS procedure will do what you want.
You can also use it to draw linestyles on the legend.

Example:

; If this is a line plot
;    Draw linestyle on legend
; Endif else
;    Draw symbol on legend
; Endelse

if jsym eq 0 then begin
   plots, [xoff+xl,xoff+xr], [ypt,ypt], linestyle=jlin, color=jcol
endif else begin
   plots, xoff+xl+xseg*0.22, ypt, psym=jsym, symsiz=sym_size, color=jcol
endelse

[This code uses DATA coordinates; I've never tried NORMAL.]


It would be nice if there were a system routine for drawing legends,
though.
Newsgroups: comp.lang.idl-pvwave
From: greg@pvi.UUCP (Greg Holling x376)
Subject: Re: signal processing package for IDL
Organization: Precision Visuals Inc., Boulder, Colorado
Date: Wed, 19 Aug 1992 16:30:13 GMT

jacobsen@bnlls1.nsls.bnl.gov (Chris Jacobsen) writes:
> To the guy with Matlab-PV~WAVE hooks:
> What about contacting Research Systems Inc, makers of IDL (the
> father and now possibly better and more bug-free peer of PV~WAVE).

The parent has some effect on the quality of the child, but that
effect is limited after the child leaves the nest.  
Give PVI some credit.  We have roughly twice as many engineers as
RSI working on bug fixes & enhancements to the original product.

'nuff said.

- Greg
-- 
Greg Holling			|	Voice: (303) 530-9000
Senior Member, Engineering	|	FAX:   (303) 530-9329
Precision Visuals, Inc.		|	boulder!pvi!greg
="Beam me up, Scotty - there's no intelligent life down here."=
From: dsims@leo.ece.uc.edu (David Sims)
Newsgroups: comp.lang.vhdl,comp.lang.verilog,comp.specification
Subject: SUMMARY: specifying hardware
Date: 13 Aug 92 14:35:59 GMT
Organization: University of Cincinnati

The following is a summary of responses to my query about specification
languages for hardware description languages such as VHDL.  Thanks to
everyone for their helpful comments.

-- David Lyle Sims (dsims@thor.ece.uc.edu)

-----

We have been doing a lot of work with state machine descriptions,
largely to do with relating CSP descriptions to stylised VHDL state
machine descriptions; we also have a way of translating occam into VHDL.

Geoff Barrett
INMOS Limited
geoffb@inmos.co.uk

*****

From: harel@wisdom.weizmann.ac.il (Harel David)

The STATEMATE system has a new vesrion, called Express-VHDL, in which a
STATEMATE model is translated automatically into a VHDL program. In case
you are not familiar with the indeas and languages underlying STATEMATE,
you should look at the papers lised below. In any event, the basic
language used is statecharts.

D. Harel, ``Biting the Silver Bullet: Toward a Brighter Future for
System Development", {\it Computer}  (Jan. 1992), 8--20.

D. Harel, H. Lachover, A. Naamad, A. Pnueli, M. Politi, R. Sherman, A.
Shtul-Trauring and M. Trakhtenbrot, ``STATEMATE: A Working Environment
for the Development of Complex Reactive Systems", {\it IEEE Transactions
on Software Engineering} {\bf 16} (1990), 403--414.

D. Harel, ``Statecharts: A Visual Formalism for Complex Systems",
{\it Science of Computer Programming,} {\bf 8} (1987), 231-274.

D. Drusinsky and D. Harel, ``Using Statecharts for Hardware Description 
and Synthesis", {\it IEEE Transactions on Computer Aided Design of 
Integrated Circuits and Systems} {\bf 8} (1989), 798--807. 

*****

Some people use HOL (higher order logic) to specify and reason about
hardware.

Two formally well-defined (but far from finished) specification
methods I know of are Victor Carreno's (vac@air16.larc.nasa.gov)
Transition Assertions (TAs) which are intended for capturing general
system behaviour and Mike Gordon's (mjcg@cl.cam.ac.uk) State
Transition Assertions (STAs) intended for describing and verifying
mixed hardware and software systems. 

*****

I have used CSP for specification, this is a new way to specify digital
systems. CSP specification is translated to VHDL code.

Milan Gandhi
mgandhi@gmuvax2.gmu.edu

*****

The following paper pertains to specifying mixed hardware/software
systems.

M.J.C. Gordon, "A Formal Method for Hard Real-Time Programming",
in "Proceedings of the 4th Refinement Workshop", J.M. Morris & R.C.
Shaw (eds), Springer-Verlag (Workshops in Computing Series), 1991.

The details in this paper are obsolete (and some of them are wrong), but
it gives the general idea.

Mike
Mike.Gordon@cl.cam.ac.uk
-- 
D. Lyle Sims                    Dept. of Electrical and Computer Engineering
dsims@thor.ece.uc.edu           University of Cincinnati
(513) 556-2499                  Cincinnati OH  45221-0030
                                USA
Newsgroups: comp.lang.vhdl
From: doug@cdc.hp.com (Doug Sojourner)
Subject: Looking for VHDL parser
Date: Wed, 12 Aug 1992 18:27:31 GMT
Reply-To: dsojourner@cdc.hp.com
Organization: Hewlett-Packard Company
X-Newsreader: Tin 1.1scd1 PL4
Keywords: VHDL, parser

I'm looking for a parser for a tool I'm developing.  Does anyone know
of any VHDL parsers which are either commercially available, or in the
public domain?  Email me, & I'll summerize to the net in a week or so.

Thanks,

--
Doug Sojourner                       Hewlett Packard Company
dsojourner@cdc.hp.com                California Design Center, 53U/84
Telnet: 1-553-3171                   5301 Stevens Creek Blvd
Phone:  (408) 553-3171               Santa Clara, CA  95052-8059
Newsgroups: comp.lang.vhdl
From: asgeir@viking.asd.sgi.com (Asgeir Eiriksson)
Subject: VHDL booklist
Organization:  Silicon Graphics, Inc.  Mountain View, CA
Date: Fri, 21 Aug 1992 17:22:30 GMT

I haven't been following this group for a while, so the following
might have been recently taken care off (in which case I'd appreciate
if someone email-ed me the conclusions).

Is there a must have VHDL booklist? I would like to hear the nets
opinion on the best book in the following categories:

 1) Introductory text
 2) Language reference
 3) Style guide/Advanced topics

and maybe

 4) books to avoid

If I get enough responses, I'll summarize to the net.

Thanks, 'Asgeir
Newsgroups: comp.lang.vhdl
From: Vidur.Kapoor@bbs.oit.unc.edu (Vidur Kapoor)
Subject: Information on synopsys, GDT software wanted
Keywords: synopsys, gdt
Organization: Extended Bulletin Board Service
Distribution: usa
Date: Thu, 20 Aug 1992 04:45:58 GMT

Dear users,
		Could someone supply me some information on gdt software from
mentor graphics or synopsys synthesis software and inform me if there are
any courses in any university in the Boston area in this subject

Thanks in advance.

vidur

You could reply to me directly at:

		vidur@orca.ele.uri.edu



--
   The opinions expressed are not necessarily those of the University of
     North Carolina at Chapel Hill, the Campus Office for Information
        Technology, or the Experimental Bulletin Board Service.
           internet:  bbs.oit.unc.edu or 152.2.22.80
From: disching@sonne (Privataccount Elmar Dischinger)
Newsgroups: comp.lang.vhdl
Subject: Looking for PD VHDL-Sources
Date: 13 Aug 92 12:55:15 GMT
Organization: PPG Hellige, Freiburg, GERMANY
X-Newsreader: Tin 1.1 PL4

Hi VHDL specialists,

can anyone give me a pointer to PD VHDL source code  
via email or ftp. email server prefered.

Thank's Elmar

 
---------------------------------------------------------------------------
NAME :  Elmar Dischinger                   |
EMAIL:  disching%ppgfr.uucp@germany.eu.net |  PPG HELLIGE 
PHONE:  (germany) 0761-4011-458 direct     |  Heinrich v. Stephan Str. 4
FAX  :  (germany) 0761-4011-446            |  D-7800 Freiburg i. Br.
---------------------------------------------------------------------------  
Newsgroups: comp.lang.vhdl
From: systat@karl.SanDiego.NCR.COM (Mehdi Bonyadi 2233)
Subject: Queue implementation
Reply-To: systat@karl.SanDiego.NCR.COM (Mehdi Bonyadi 2233)
Organization: NCR Corp. E & M San Diego
Distribution: usa
Date: Wed, 12 Aug 1992 23:11:42 GMT

I need to implement a queue of transactions in VHDL and if anyone out
there had already done this or anything similar to it, I would
appreciate it if you could share it with me.

Many thanks 
Mehdi
mehdi@venus.SanDiego.NCR.COM

Newsgroups: comp.lang.vhdl
From: doug@cdc.hp.com (Doug Sojourner)
Subject: Re: Looking for VHDL parser
Date: Wed, 19 Aug 1992 17:53:29 GMT
Reply-To: dsojourner@cdc.hp.com
Organization: HP California Design Center, Santa Clara, CA
X-Newsreader: Tin 1.1scd1 PL4

Here's the summary I promised:

From: Dave Alford <davida@netcom.com>
	Commercial parser from Cad Language Systems, Inc.

	Commercial parser from Seed Solutions
		Seeds VHDL ENvironment (SVEN)
		Seed Solutions, Inc.
		7505 Sherman Road
		Chesterland, OH 44026
		216-729-7500

From: helmut@zycad.com (Helmut Hissen - MP)
	CLSI parser is slow to learn, but has consistent interface.
	Parser is "picky", sticking close to LRM. Good product &
	documentation, support/service not too good.

From: aranake@cse.uta.edu (Sandeep Suresh Aranake)
(quoted from Thomas Dettmer in the FAQ)
	Public Domain parser in Prolog from 
		Microelectronics Center of North Carolina
		anonymous FTP from MCNC.ORG /pub/vhdl.tar.Z

	Public Domain? grammar suited for lex & yacc, validation suite
		anonymous FTP on uceng.uc.edu

From: Peter Reintjes <sofla!pbr@quintus.com>
	Corrected & improved version of above Prolog parser part of
		ECAD library version 1.0.
		Jim Treyens
		Quintus 
		1(800)542-1283

	Version 2.0 will have more BNF discription, and other HDL's
	

--
Doug Sojourner                       Hewlett Packard Company
dsojourner@cdc.hp.com                California Design Center, 53U/84
Telnet: 1-553-3171                   5301 Stevens Creek Blvd
Phone:  (408) 553-3171               Santa Clara, CA  95052-8059
From: hai@hpfcso.FC.HP.COM (Hai Vo-Ba)
Date: Fri, 21 Aug 1992 14:15:08 GMT
Subject: Verilog to TEGAS translator
Organization: Hewlett-Packard, Fort Collins, CO, USA