| Anonymous | Login | 2010-09-09 00:02 PDT |
| Main | My View | View Issues | Docs | Wiki |
| Viewing Issue Simple Details [ Jump to Notes ] [ Wiki ] | [ View Advanced ] [ Issue History ] [ Print ] | |||||||||||
| ID | Category | Severity | Date Submitted | Last Update | ||||||||
| 0002643 | [SystemVerilog P1800] SV-BC | minor | 2009-04-06 14:05 | 2009-07-10 09:01 | ||||||||
| Reporter | chas | View Status | public | |||||||||
| Assigned To | ||||||||||||
| Priority | normal | Resolution | reopened | |||||||||
| Status | feedback | Product Version | P1800-2009/D8 Ballot | |||||||||
| Summary | 0002643: Ballot comment #152 Section implies that a SystemVerilog function cannot be disabled | |||||||||||
| Description |
Section 9.6.2, Page 167 (201), states: "The disable statement can be used to disable named blocks within a function, but cannot be used to disable functions. In cases where a disable statement within a function disables a block or a task that called the function, the behavior is undefined.". This implies that a SystemVerilog function cannot be disabled. This is in contradiction of the disable protocol for DPI import functions, item c in the disable protocol. See page 859 (893) in clause 35.9 from the 2009 ballot draft 1. |
|||||||||||
| Additional Information |
Proposed change from the ballot comment: Since the behavior on disabling of a function is undefined the disable protocol should apply only to tasks. Whenever, the disable protocol is applied to a function, the behavior should be undefined. |
|||||||||||
| Tags | No tags attached. | |||||||||||
| Type | Enhancement | |||||||||||
| Attached Files | ||||||||||||
|
|
||||||||||||
Relationships |
||||||||||||||||
|
||||||||||||||||
Notes |
|
|
shalom (manager) 2009-04-06 23:45 |
Ballot comments 151 and 152 (0002642 and this one) appear to be the same issue, but with different desired resolutions. |
|
mmaidment (manager) 2009-05-03 23:45 |
On April 27, 2009 the SV-BC read and considered this feedback. The committee believes it is too broad for the scope of the draft to implement at this time but may be considered for future revisions. |
|
Neil Korpusik (administrator) 2009-05-16 19:32 |
The resolution of "open" was unanimously approved by the Champions in the email vote that ended on May 14th, 2009. |
|
Neil Korpusik (administrator) 2009-06-01 10:30 |
The resolution of "open" was unanimously approved by the Working Group in the conference call of May 28, 2009. Closing this mantis item. |
|
Dave Rich (manager) 2009-07-10 09:01 |
Rather than create a new mantis issue, this will be left in the feedback state for the committee to deal with in the next PAR. |
| Mantis 1.1.7[^] Copyright © 2000 - 2008 Mantis Group |