The main problem is what to do about users overriding the builtin definitions of system tasks such as $display. Things like $display (et al) have had well-defined meanings for so long that I don't think we want to mess around with them. Since there isn't a problem with systasks in general, if someone wanted to write up an explicit exclusion for them in the context of functions, that would be fine. Gord Brad Pierce wrote: > Is there anything task-like about $display, or should it really be a > void system function? > > -- Brad > > ------------------------------------------------------------------------ > *From:* owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] *On Behalf Of > *Bresticker, Shalom > *Sent:* Monday, September 03, 2007 5:30 AM > *To:* sv-bc > *Subject:* [sv-bc] function task calling > > Since functions are not allowed to call tasks, how can a function > contain a call to $display? > > What types of built-in system tasks are functions allowed to call? > > Shalom > > Shalom Bresticker > Intel Jerusalem LAD DA > +972 2 589-6852 > +972 54 721-1033 > > > -- > This message has been scanned for viruses and > dangerous content by *MailScanner* <http://www.mailscanner.info/>*, and is > believed to be clean. > -- > This message has been scanned for viruses and > dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is > believed to be clean. * -- -------------------------------------------------------------------- Gordon Vreugdenhil 503-685-0808 Model Technology (Mentor Graphics) gordonv@model.com -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Tue Sep 4 07:21:04 2007
This archive was generated by hypermail 2.1.8 : Tue Sep 04 2007 - 07:21:24 PDT