>From: "Rich, Dave" <Dave_Rich@mentor.com> >You and I have too long a history with Verilog. The only reason we call >system tasks "tasks" is because there were no void function in Verilog. I would say you are reversing what is "normal" in a language here :-) Most languages with subroutines have two distinct types, with different names: functions which return values, and tasks/procedures which don't. It was C that was abnormal in only having functions. In ANSI C, this was changed by allowing them to have a void return type, effectively adding tasks/procedures in a kludgey way. Verilog already had the concept of a task, like most languages do. It didn't need void functions for that. The only reason we call nonblocking tasks "void functions" in Verilog is because the Superlog developers had too long a history with C. Steven Sharp sharp@cadence.com -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Mon Sep 10 19:17:54 2007
This archive was generated by hypermail 2.1.8 : Mon Sep 10 2007 - 19:18:08 PDT