Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

parse error with nested list #166

Closed
veripoolbot opened this issue Feb 9, 2009 · 0 comments
Closed

parse error with nested list #166

veripoolbot opened this issue Feb 9, 2009 · 0 comments
Assignees

Comments

@veripoolbot
Copy link
Collaborator


Author Name: Devendra Singh
Original Redmine Issue: 166 from https://www.veripool.org
Original Date: 2009-02-09
Original Assignee: Wilson Snyder (@wsnyder)


This bug was cloned from Perl-RT, rt43138.

Email addresses have have been truncated.

Id: 	43138
Status: 	resolved
Left: 	0 min
Queue: 	Verilog-Perl
Owner: 	Nobody
Requestors: 	dbsingh1880 <devendra.singh@>

Severity: 	Important
Broken in: 	3.110

Mon Feb 09 05:41:48 2009 dbsingh1880 - Ticket created

Subject: 	parse error with nested list

if nested assignment (multiple "{{") is used the parser generates
error....
example code with response is provided below

==================example code======================================
module am
(/*autoarg*/);

output a,b,c,d,e,f;
input@z;
wire a,b,c,d,e,f;

assign {{a,b},c,d,e,f} = z;
endmodule // am

=======================response======================================
[root@punelabpc10 /tmp]$ vhier am.v
%Error: am.v:8: syntax error, unexpected '{', expecting "IDENTIFIER"
Exiting due to errors
[root@punelabpc10 /tmp]$

Mon Feb 09 05:42:03 2009 dbsingh1880 - Status changed from 'new' to 'open'

Mon Feb 09 07:53:55 2009 WSNYDER - Correspondence added

Thanks for the report. I fixed this in the GIT version available from
veripool.org and this will be in the next release.

If there's more issues please use the bug reporter on veripool.org as
it's less work for me, thanks.

Mon Feb 09 07:53:55 2009 WSNYDER - Status changed from 'open' to 'resolved'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants