( ESNUG 223 Item 1 ) ---------------------------------------------- [7/26/95]
Subject: (ESNUG 215 #5 217 #4 220 #4) Specific Reasons Why Synopsys Sucks!
>Not only that, but the *extensive* help almost never leaves you stranded.
>How many tools allow you to do things like 'help HDL-103' to get an extended
>description of why its unhappy along with instructions for what to try next?
>In fact, just as a test, I just tried to read in a non-existent file:
>
> design_combobulator>read -f vhdl none.vhd
> Error: Cannot read file 'none.vhd'. (UID-58)
> {}
>
>Now, just in case that's not enough information, I could do:
> design_combobulator>help UID-58
From: biswal@india.ti.com (Krutibas Biswal)
John,
I don't agree with this point. Yes, Synopsys has this feature, but the help
it prints are not always sufficient. Let us take for example if the above
command "read -f vhdl foo.vhd" fails, then it is obvious and intuitive that
either the file does not exist or the file has no read permissions. 90+% of
Synopsys users won't need an explanation for this. But trying "help SYNDB-3"
will get you a truely incomprehensive message when you REALLY need help.
design_analyzer> help SYNDB-3
or try, help SYNDB 1, 10, 11, 12, 13, DB-4, DDP-<n>, where <n> is any number!
There is no point in providing a feature which is not actually there.
- Krutibas Biswal
Texas Instruments (India) Pvt Ltd
|
|
