On Saturday, May 05, 2012 06:32:47 PM andy pugh did opine: > On 5 May 2012 18:24, gene heskett <[email protected]> wrote: > > So I cannot use that signal1 defined name as an 'out1' in another net > > statement, but must add the other targets/pins in the same line it is > > defined in. > > No, that is all wrong too. > > Every "net" command is followed immediately by a signal name. That is, > a name you have chosen yourself, to make sense to you (or to confuse > yourself horribly in the future, if you so choose). > You can uses the same signal name on as many net commands as you like. > But being a signal name it needs to be the first term after the word > "net" > Every "net" command with the same signal name will pass the same value > to every HAL pin listed in the command. And that value will be from > the one, and only one, output pin that appears in one of the net > commands. > > You can even not bother with the output pin if you want, and set the > signal name directly with sets.
Thanks Andy, the lights are slowly getting brighter. Cheers, Gene -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) My web page: <http://coyoteden.dyndns-free.com:85/gene> Pascal: A programming language named after a man who would turn over in his grave if he knew about it. -- Datamation, January 15, 1984 ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
