Message handling - Revision history

Mohammad at 19:48, 12 December 2023

2023-12-12T19:48:23Z

2023-12-07T23:48:00Z

2023-12-07T23:43:05Z

2023-12-07T23:33:11Z

2021-07-30T04:20:28Z

2021-03-05T00:06:31Z

2021-02-26T01:11:55Z

2021-02-26T01:11:37Z

2020-12-07T20:18:18Z

2020-06-03T00:47:05Z

@@ Line 32: / Line 32: @@
 Message.ClearAllMessageTypes() - Clear all forced message types
-Now instead of 'Message_SetMessageType()' Python interface accepts 'Message.SetMessageType()' to make the code more readable.
+* Python interface also accepts 'Message_SetMessageType()' but 'Message.SetMessageType()' is accepted and is more readable.
   </nowiki>
 Some Python usage example:
@@ Line 44: / Line 44: @@
 ../../src/example_designs/verilog/r4000.v(84): INFO: analyzing included file '../../src/example_designs/verilog/register.v' (VERI-1328)
 ../../src/example_designs/verilog/r4000.v(84): INFO: back to file '../../src/example_designs/verilog/r4000.v' (VERI-2320)
-−
 This python line is added before analyzing the file:
 Verific.Message.SetMessageType("VERI-1328", Verific.VERIFIC_IGNORE)
-−
 New messages log:
 -- Analyzing Verilog file '../../src/example_designs/verilog/r4000.v' (VERI-1482)

@@ Line 45: / Line 45: @@
 ../../src/example_designs/verilog/r4000.v(84): INFO: back to file '../../src/example_designs/verilog/r4000.v' (VERI-2320)
-After this python line is added:
+This python line is added before analyzing the file:
 Verific.Message.SetMessageType("VERI-1328", Verific.VERIFIC_IGNORE)

@@ Line 26: / Line 26: @@
 For Python, use the following APIs:
   <nowiki>
-Message_SetMessageType()       - Force a message type by message id
+Message.SetMessageType()       - Force a message type by message id
-Message_GetMessageType()       - Get the message type by message id
+Message.GetMessageType()       - Get the message type by message id
-Message_ClearMessageType()     - Clear a message type by message id
+Message.ClearMessageType()     - Clear a message type by message id
-Message_SetAllMessageType()    - Force all messages of type 'orig' to behave as type 'type'.
+Message.SetAllMessageType()    - Force all messages of type 'orig' to behave as type 'type'.
-Message_ClearAllMessageTypes() - Clear all forced message types
+Message.ClearAllMessageTypes() - Clear all forced message types
   </nowiki>
 Some Python usage example:
@@ Line 44: / Line 46: @@
 After this python line is added:
-Verific.Message_SetMessageType("VERI-1328", Verific.VERIFIC_IGNORE)
+Verific.Message.SetMessageType("VERI-1328", Verific.VERIFIC_IGNORE)
 New messages log:

@@ Line 23: / Line 23: @@
 Message::ClearAllMessageTypes() - Clear all forced message types
   </nowiki>
 For Tcl, use the following commands:
   <nowiki>

@@ Line 40: / Line 40: @@
 '''Q: How do I get messages with more details?'''
-For "syntax error" messages, you can get messages with more details by enabling compile flag "VERIFIC_PRODUCE_VERBOSE_SYNTAX_ERROR_MESSAGE" or its runtime equivalent "verific_produce_verbose_syntax_error_message."
+For "syntax error" messages, you can get messages with more details by enabling compile flag "VERIFIC_PRODUCE_VERBOSE_SYNTAX_ERROR_MESSAGE" or its runtime equivalent "verific_produce_verbose_syntax_error_message".
 With these flags enabled, for syntax errors, the parsers will print the whole line and point to the exact token where the issue is.

@@ Line 42: / Line 42: @@
 For "syntax error" messages, you can get messages with more details by enabling compile flag "VERIFIC_PRODUCE_VERBOSE_SYNTAX_ERROR_MESSAGE" or its runtime equivalent "verific_produce_verbose_syntax_error_message."
-With these flags enabled, for syntax errors, the parsers will print the whole line and point to the token where the issue is. they also print the expected tokens that may fix the issue.
+With these flags enabled, for syntax errors, the parsers will print the whole line and point to the exact token where the issue is.
 For example, with:

@@ Line 1: / Line 1: @@
 '''Q: How do I upgrade/downgrade messages from Verific?'''
-Verific message table, with notation as whether the error can be safely downgraded: [http://www.verific.com/docs/index.php?title=Message_Downgrading_Table "Verific Message Table"]
+Verific message table, with notation as whether the error can be safely downgraded: [http://www.verific.com/docs/index.php?title=Message_Downgrading_Table Verific Message Table]
 (Access to Verific On-line Documentation requires login. Contact Verific if you don't know/don't have credentials).

@@ Line 88: / Line 88: @@
 test.v(7): ERROR: module 'test' ignored due to previous errors (VERI-1072)
 ERROR: analyze: failed (CMD-1014)
   </nowiki>

@@ Line 8: / Line 8: @@
 You can set any message to any type below:
-For C++, use the following APIs:
+'''Q: How do I get messages with more details?'''
- Message::SetMessageType()       - Force a message type by message id
- Message::GetMessageType()       - Get the message type by message id
- Message::ClearMessageType()     - Clear a message type by message id
- Message::SetAllMessageType()    - Force all messages of type 'orig' to behave as type 'type'.
- Message::ClearAllMessageTypes() - Clear all forced message types
-For Tcl, use the following commands:
+For "syntax error" messages, you can get messages with more details by enabling compile flag "VERIFIC_PRODUCE_VERBOSE_SYNTAX_ERROR_MESSAGE" or its runtime equivalent "verific_produce_verbose_syntax_error_message."
- setmsgtype
- clearmsgtype
-Some Perl command examples:
+With these flags enabled, for syntax errors, the parsers will print the whole line and point to the token where the issue is. they also print the expected tokens that may fix the issue.
-−
- # ignore message VNLR-1015
- Verific::Message::SetMessageType("VNLR-1015", $Verific::VERIFIC_IGNORE);
- # ignore all warning messages
- Verific::Message::SetAllMessageType($Verific::VERIFIC_WARNING, $Verific::VERIFIC_IGNORE);
-Note that downgrading an error may have unpredictable/undesirable results.
+For example, with: