Mail Index

• Thread Index

• Language TF mailing list
  • From: Yaron Kashai <yaron@verisity.com>
• Message from Chris
  • From: Yaron Kashai <yaron@verisity.com>
• IEEE 1647 BL TF Kick Off
  • From: Chris Macionski <chris@brighteyesconsulting.com>
• Re: IEEE 1647 BL TF Kick Off
  • From: Avi Bloch <avi@verisity.com>
• Re: IEEE 1647 BL TF Kick Off
  • From: Chris Macionski <chris@brighteyesconsulting.com>
• RE: IEEE 1647 BL TF Kick Off
  • From: "Silas McDermott" <silas@verisity.com>
• Re: IEEE 1647 BL TF Kick Off
  • From: Cristian Amitroaie <cristian@amiq.ro>
• IEEE 1647 BL TF Kick Off Reminder
  • From: Chris Macionski <chris@brighteyesconsulting.com>
• Re: IEEE 1647 BL TF Kick Off Reminder
  • From: Chris Macionski <chris@brighteyesconsulting.com>
• Test, please ignore
  • From: Yaron Kashai <yaron@verisity.com>
• Notes from BL TF Meeting
  • From: Chris Macionski <chris@brighteyesconsulting.com>
• keyword list - need help from other task forces
  • From: Cristian Amitroaie <cristian@amiq.ro>
• issue tracking vs. task force internals
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: issue tracking vs. task force internals
  • From: Chris Macionski <chris@brighteyesconsulting.com>
• Elsif Syntax
  • From: Chris Macionski <chris@brighteyesconsulting.com>
• Index-name recommendation
  • From: Chris Macionski <chris.work@bigari.com>
• For each line in file...
  • From: Chris Macionski <chris.work@bigari.com>
• Re: For each line in file...
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: Index-name recommendation
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: Elsif Syntax
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Reminder- BL TF Meeting Tomorrow
  • From: Chris Macionski <chris.work@bigari.com>
• RE: Index-name recommendation
  • From: "Silas McDermott" <silas@verisity.com>
• RE: For each line in file...
  • From: "Silas McDermott" <silas@verisity.com>
• RE: Elsif Syntax
  • From: "Silas McDermott" <silas@verisity.com>
• Re: Index-name recommendation
  • From: Chris Macionski <chris.work@bigari.com>
• Re: For each line in file...
  • From: Chris Macionski <chris.work@bigari.com>
• Re: For each line in file...
  • From: Chris Macionski <chris.work@bigari.com>
• RE: For each line in file...
  • From: "Silas McDermott" <silas@verisity.com>
• Re: For each line in file...
  • From: Avi Bloch <avi@verisity.com>
• Re: Elsif Syntax
  • From: Avi Bloch <avi@verisity.com>
• Re: For each line in file...
  • From: Chris Macionski <chris.work@bigari.com>
• Issue Submitting
  • From: Chris Macionski <chris.work@bigari.com>
• Notes from Meeting 2/4/04
  • From: Chris Macionski <chris.work@bigari.com>
• Fwd: Questions from the BL TF Meeting
  • From: Chris Macionski <chris.work@bigari.com>
• Submitted issues
  • From: Chris Macionski <chris.work@bigari.com>
• Fwd: Recommendations in the LRM
  • From: Chris Macionski <chris@brighteyesconsulting.com>
• An interesting language issue
  • From: Yaron Kashai <yaron@verisity.com>
• Next BL TF Meeting
  • From: Chris Macionski <chris.work@bigari.com>
• C interface in e LRM
  • From: Avi Bloch <avi@verisity.com>
• Fwd: C interface in e LRM
  • From: Chris Macionski <chris.work@bigari.com>
• Re: C interface in e LRM
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Reminder- BL TF Meeting tomorrow
  • From: Chris Macionski <chris.work@bigari.com>
• Couple of reminders
  • From: Chris Macionski <chris@brighteyesconsulting.com>
• Re: Couple of reminders
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: Reminder- BL TF Meeting tomorrow
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: Reminder- BL TF Meeting tomorrow
  • From: Chris Macionski <chris.work@bigari.com>
• Re: Reminder- BL TF Meeting tomorrow
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: Reminder- BL TF Meeting tomorrow
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Logged off
  • From: "Silas McDermott" <silas@verisity.com>
• Pls. see BNF posting
  • From: Yaron Kashai <yaron@verisity.com>
• Notes from 3/31 BL TF Meeting
  • From: Chris Macionski <chris.work@bigari.com>
• keywords and reserved names
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: keywords and reserved names
  • From: Chris Macionski <chris.work@bigari.com>
• Re: keywords and reserved names
  • From: Yaron Kashai <yaron@verisity.com>
• Re: keywords and reserved names
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: keywords and reserved names
  • From: Chris Macionski <chris.work@bigari.com>
• Re: keywords and reserved names
  • From: Yaron Kashai <yaron@verisity.com>
• Re: keywords and reserved names
  • From: Yaron Kashai <yaron@verisity.com>
• Re: keywords and reserved names
  • From: Ron Bow <ronb@verisity.com>
• Re: keywords and reserved names
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: keywords and reserved names
  • From: Chris Macionski <chris.work@bigari.com>
• keywords - call for final agreement
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: Notes from 3/31 BL TF Meeting
  • From: Avi Bloch <avi@verisity.com>
• Reminder IEEE1647 Meeting today
  • From: Chris Macionski <chris.work@bigari.com>
• Notes from May6 Meeting
  • From: Chris Macionski <chris.work@bigari.com>
• [Issue 56] 2.3.3 Implicit Variables - mising prev
  • From: Cristian Amitroaie <cristian@amiq.ro>
• [Issue 34] File Names
  • From: Cristian Amitroaie <cristian@amiq.ro>
• [Issue 37] 2.1.5.1 Legal e name - Names begining with an underscore have a special meaning in e?
  • From: Cristian Amitroaie <cristian@amiq.ro>
• [Issue 54] 2.3.3 Implicit Variables - using result in pathnames
  • From: Cristian Amitroaie <cristian@amiq.ro>
• [Issue 50] 2.5 Evaluation Order of Expressions - ambiguous predictability
  • From: Cristian Amitroaie <cristian@amiq.ro>
• [Issue 65]2.6.3 >>, << - The result of a shift by more than 31 bits is undefined
  • From: Cristian Amitroaie <cristian@amiq.ro>
• [Issue 133]2.11.1 [] - interpreted vs. compiled checks
  • From: Cristian Amitroaie <cristian@amiq.ro>
• [Issue 122]2.10 String Matching - legal e names and $0, $1 from string matching
  • From: Cristian Amitroaie <cristian@amiq.ro>
• [Issue 125] 2.1.4.2 Sized Numbers - the use of hyphen is missing
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: [Issue 34] File Names
  • From: Chris Macionski <chris.work@bigari.com>
• Re: [Issue 56] 2.3.3 Implicit Variables - mising prev
  • From: Chris Macionski <chris.work@bigari.com>
• Re: [Issue 37] 2.1.5.1 Legal e name - Names begining with an underscore have a special meaning in e?
  • From: Chris Macionski <chris.work@bigari.com>
• Re: [Issue 54] 2.3.3 Implicit Variables - using result in pathnames
  • From: Chris Macionski <chris.work@bigari.com>
• Re: [Issue 50] 2.5 Evaluation Order of Expressions - ambiguous predictability
  • From: Chris Macionski <chris.work@bigari.com>
• Re: [Issue 65]2.6.3 >>, << - The result of a shift by more than 31 bits is undefined
  • From: Chris Macionski <chris.work@bigari.com>
• Re: [Issue 133]2.11.1 [] - interpreted vs. compiled checks
  • From: Chris Macionski <chris.work@bigari.com>
• Re: [Issue 122]2.10 String Matching - legal e names and $0, $1 from string matching
  • From: Chris Macionski <chris.work@bigari.com>
• Re: [Issue 125] 2.1.4.2 Sized Numbers - the use of hyphen is missing
  • From: Chris Macionski <chris.work@bigari.com>
• Re: [Issue 56] 2.3.3 Implicit Variables - mising prev
  • From: Avi Bloch <avi@verisity.com>
• Re: [Issue 37] 2.1.5.1 Legal e name - Names begining with an underscorehave a special meaning in e?
  • From: Avi Bloch <avi@verisity.com>
• Re: [Issue 54] 2.3.3 Implicit Variables - using result in pathnames
  • From: Avi Bloch <avi@verisity.com>
• [Issue 160] 2.12 [range, ..] expressions in range
  • From: Cristian Amitroaie <cristian@amiq.ro>
• [Issue 161] 2.12 [range, ..] is bit[1..10] legal?
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: [Issue 160] 2.12 [range, ..] expressions in range
  • From: Chris Macionski <chris.work@bigari.com>
• Re: [Issue 161] 2.12 [range, ..] is bit[1..10] legal?
  • From: Chris Macionski <chris.work@bigari.com>
• Re: [Issue 161] 2.12 [range, ..] is bit[1..10] legal?
  • From: Yaron Kashai <yaron@verisity.com>
• Re: [Issue 160] 2.12 [range, ..] expressions in range
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: [Issue 160] 2.12 [range, ..] expressions in range
  • From: Chris Macionski <chris.work@bigari.com>
• [Issue 167] 2.15.3 . (dereference operator)
  • From: Cristian Amitroaie <cristian@amiq.ro>
• [Issue 164] 2.12.2 (bits | bytes : width-exp) Should bit(bits:10) be legal?
  • From: Cristian Amitroaie <cristian@amiq.ro>
• BLTF- Meeting Reminder
  • From: Chris Macionski <chris@brighteyesconsulting.com>
• Re: [Issue 34] File Names
  • From: Avi Bloch <avi@verisity.com>
• Re: [Issue 50] 2.5 Evaluation Order of Expressions - ambiguous predictability
  • From: Avi Bloch <avi@verisity.com>
• Re: [Issue 65]2.6.3 >>, << - The result of a shift by more than 31bits is undefined
  • From: Avi Bloch <avi@verisity.com>
• Re: [Issue 133]2.11.1 [] - interpreted vs. compiled checks
  • From: Avi Bloch <avi@verisity.com>
• Re: [Issue 34] File Names
  • From: Chris Macionski <chris.work@bigari.com>
• Re: BLTF- Meeting Reminder
  • From: Chris Macionski <chris.work@bigari.com>
• Re: BLTF- Meeting Reminder
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: BLTF- Meeting Reminder
  • From: Chris Macionski <chris.work@bigari.com>
• Re: BLTF- Meeting Reminder
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: BLTF- Meeting Reminder
  • From: Avi Bloch <avi@verisity.com>
• Re: BLTF- Meeting Reminder
  • From: Chris Macionski <chris.work@bigari.com>
• RE: BLTF- Meeting Reminder
  • From: "Silas McDermott" <silas@verisity.com>
• Re: BLTF- Meeting Reminder
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Reminder: Meeting Jun 29
  • From: Chris Macionski <chris@brighteyesconsulting.com>
• New LRM schedule
  • From: Chris Macionski <chris.work@bigari.com>
• Task Force Update
  • From: Chris Macionski <chris.work@bigari.com>
• Work Plan
  • From: Chris Macionski <chris.work@bigari.com>
• Re: Work Plan
  • From: Chris Macionski <chris.work@bigari.com>
• Re: Work plans
  • From: Chris Macionski <chris.work@bigari.com>
• Meeting moved
  • From: Chris Macionski <chris.work@bigari.com>
• Re: Meeting moved
  • From: Avi Bloch <avi@verisity.com>
• RE: Meeting moved
  • From: "Silas McDermott" <silas@verisity.com>
• Re: Meeting moved
  • From: Chris Macionski <chris.work@bigari.com>
• Fwd: Work plans
  • From: Chris Macionski <chris.work@bigari.com>
• 1647 Meetings Next Week
  • From: Chris Macionski <chris@brighteyesconsulting.com>
• Re: 1647 Meetings Next Week
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Pending issues
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: the keywords doc
  • From: Yaron Kashai <yaron@verisity.com>
• Re: Pending issues
  • From: Chris Macionski <chris@brighteyesconsulting.com>
• RE: Pending issues
  • From: "Silas McDermott" <silas@verisity.com>
• Re: Pending issues
  • From: Avi Bloch <avi@verisity.com>
• Re: Pending issues
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: Pending issues
  • From: Chris Macionski <chris.work@bigari.com>
• IEEE1647 BLTF Meeting
  • From: Chris Macionski <chris@brighteyesconsulting.com>
• Fwd: LRM 0.2 & pending issues
  • From: Chris Macionski <chris@brighteyesconsulting.com>
• Re: Pending issues
  • From: Cristian Amitroaie <cristian@amiq.ro>
• final keywords doc
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: ieee1647 - keyword issue
  • From: Chris Macionski <chris.work@bigari.com>
• Re: ieee1647 - keyword issue
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: ieee1647 - keyword issue
  • From: Chris Macionski <chris.work@bigari.com>
• RE: ieee1647 - keyword issue
  • From: "Matan Vax" <matan@verisity.com>
• Re: ieee1647 - keyword issue
  • From: Cristian Amitroaie <cristian@amiq.ro>
• RE: ieee1647 - keyword issue
  • From: "Matan Vax" <matan@verisity.com>
• limit of 14 parameters
  • From: Avi Bloch <avi@verisity.com>
• inline methods
  • From: Avi Bloch <avi@verisity.com>
• Re: limit of 14 parameters
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: inline methods
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: limit of 14 parameters
  • From: Chris Macionski <chris.work@bigari.com>
• Re: inline methods
  • From: Chris Macionski <chris.work@bigari.com>
• RE: limit of 14 parameters
  • From: "Silas McDermott" <silas@verisity.com>
• RE: inline methods
  • From: "Silas McDermott" <silas@verisity.com>
• Re: limit of 14 parameters
  • From: Avi Bloch <avi@verisity.com>
• Re: inline methods
  • From: Avi Bloch <avi@verisity.com>
• Re: inline methods
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Meeting on Monday
  • From: Chris Macionski <chris.work@bigari.com>
• Re: Meeting on Monday
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: Meeting on Monday
  • From: Chris Macionski <chris.work@bigari.com>
• keywords, macros, standard
  • From: Cristian Amitroaie <cristian@amiq.ro>
• BLTF Meeting Tomorrow
  • From: Chris Macionski <chris@brighteyesconsulting.com>
• Re: BLTF Meeting Tomorrow
  • From: Avi Bloch <avi@verisity.com>
• RE: BLTF Meeting Tomorrow
  • From: "Silas McDermott" <silas@verisity.com>
• Re: BLTF Meeting Tomorrow
  • From: Chris Macionski <chris@brighteyesconsulting.com>
• Won't make meeting today
  • From: Chris Macionski <chris.work@bigari.com>
• Any upcoming issues?
  • From: Chris Macionski <chris.work@bigari.com>
• RE: Any upcoming issues?
  • From: "Silas McDermott" <silas@verisity.com>
• Re: Any upcoming issues?
  • From: Chris Macionski <chris.work@bigari.com>
• Need for a meeting?
  • From: Chris Macionski <chris.work@bigari.com>
• Re: Need for a meeting?
  • From: Cristian Amitroaie <cristian@amiq.ro>
• print syntax
  • From: Cristian Amitroaie <cristian@amiq.ro>
• print format
  • From: Cristian Amitroaie <cristian@amiq.ro>
• dut_errorf
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: print syntax
  • From: Chris Macionski <chris.work@bigari.com>
• Re: print format
  • From: Chris Macionski <chris.work@bigari.com>
• Re: dut_errorf
  • From: Chris Macionski <chris.work@bigari.com>
• RE: print syntax
  • From: "Silas McDermott" <silas@cadence.com>
• Re: print format
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: print syntax
  • From: Cristian Amitroaie <cristian@amiq.ro>
• predefined "session" fields and check that
  • From: Cristian Amitroaie <cristian@amiq.ro>
• verify that an expect was successfully performed
  • From: Cristian Amitroaie <cristian@amiq.ro>
• dut_error_struct.message
  • From: Cristian Amitroaie <cristian@amiq.ro>
• need more details about the dut_error_struct
  • From: Cristian Amitroaie <cristian@amiq.ro>
• set_check() and static_match
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: print syntax
  • From: Cristian Amitroaie <cristian@amiq.ro>
• RE: print syntax
  • From: "Silas McDermott" <silas@cadence.com>
• IEEE 1674 BLTF Meeting
  • From: Chris Macionski <chris.work@bigari.com>
• Re: IEEE 1674 BLTF Meeting
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: IEEE 1674 BLTF Meeting
  • From: Chris Macionski <chris.work@bigari.com>
• Re: IEEE 1674 BLTF Meeting
  • From: Avi Bloch <avibl@cadence.com>
• Re: IEEE 1674 BLTF Meeting
  • From: Chris Macionski <chris.work@bigari.com>
• Notes from 6/28/05 Meeting
  • From: Chris Macionski <chris@brighteyesconsulting.com>
• RE: Notes from 6/28/05 Meeting
  • From: "Yaron Kashai" <yaron@cadence.com>
• Re: Notes from 6/28/05 Meeting
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: Notes from 6/28/05 Meeting
  • From: Avi Bloch <avibl@cadence.com>
• Re: Names beginning with underscore
  • From: Cristian Amitroaie <cristian@amiq.ro>
• RE: Names beginning with underscore
  • From: "Matan Vax" <matan@cadence.com>
• Concerning the new category "range"
  • From: "Matan Vax" <matan@cadence.com>
• Misleading section in chapter 2
  • From: "Matan Vax" <matan@cadence.com>
• RE: Names beginning with underscore
  • From: "Yaron Kashai" <yaron@cadence.com>
• Re: Misleading section in chapter 2
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: Concerning the new category "range"
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Issues with section 2.2.1
  • From: "Matan Vax" <matan@cadence.com>
• RE: Misleading section in chapter 2
  • From: "Yaron Kashai" <yaron@cadence.com>
• "require-tf-review" issues
  • From: "Yaron Kashai" <yaron@cadence.com>
• Re: Misleading section in chapter 2
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: "require-tf-review" issues
  • From: Chris Macionski <chris.work@bigari.com>
• Getting closure on some open issues
  • From: "Yaron Kashai" <yaron@cadence.com>
• RE: Getting closure on some open issues
  • From: "Matan Vax" <matan@cadence.com>
• Re: Getting closure on some open issues
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: Getting closure on some open issues
  • From: Cristian Amitroaie <cristian@amiq.ro>
• Re: "require-tf-review" issues
  • From: Cristian Amitroaie <cristian@amiq.ro>
• issue 459: reserving macro non-terminals (e.g. "statement" appears in <s'statement>)
  • From: Cristian Amitroaie <cristian@amiq.ro>
• RE: issue 459: reserving macro non-terminals (e.g. "statement" appears in <s'statement>)
  • From: "Matan Vax" <matan@cadence.com>
• Re: issue 459: reserving macro non-terminals (e.g. "statement" appears in <s'statement>)
  • From: Cristian Amitroaie <cristian@amiq.ro>
• RE: issue 459: reserving macro non-terminals (e.g. "statement" appears in <s'statement>)
  • From: "Matan Vax" <matan@cadence.com>
• Re: Getting closure on some open issues
  • From: Chris Macionski <chris.work@bigari.com>
• RE: Getting closure on some open issues
  • From: "Yaron Kashai" <yaron@cadence.com>
• RE: Getting closure on some open issues
  • From: "Yaron Kashai" <yaron@cadence.com>
• Re: Getting closure on some open issues
  • From: Chris Macionski <chris.work@bigari.com>
• RE: issue 459: reserving macro non-terminals (e.g. "statement" appears in <s'statement>)
  • From: "Yaron Kashai" <yaron@cadence.com>
• Re: Getting closure on some open issues
  • From: Cristian Amitroaie <cristian@amiq.ro>
• macros and syntactic parsing
  • From: Cristian Amitroaie <cristian@amiq.ro>
• About range modifiers
  • From: "Yaron Kashai" <yaron@cadence.com>
• Re: About range modifiers
  • From: Cristian Amitroaie <cristian@amiq.ro>
• RE: About range modifiers
  • From: "Yaron Kashai" <yaron@cadence.com>
• About DUT error action blocks
  • From: "Yaron Kashai" <yaron@cadence.com>
• RE: About DUT error action blocks
  • From: "Mark Strickland \(mastrick\)" <mastrick@cisco.com>
• RE: About DUT error action blocks
  • From: "Yaron Kashai" <yaron@cadence.com>