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

adapt Verilog::Getopt to recent releases of Getopt::Long #167

Closed
veripoolbot opened this issue Jun 17, 2009 · 0 comments
Closed

adapt Verilog::Getopt to recent releases of Getopt::Long #167

veripoolbot opened this issue Jun 17, 2009 · 0 comments
Assignees

Comments

@veripoolbot
Copy link
Collaborator

@veripoolbot veripoolbot commented Jun 17, 2009


Author Name: Marek Rouchal
Original Redmine Issue: 167 from https://www.veripool.org
Original Date: 2009-06-17
Original Assignee: Wilson Snyder (@wsnyder)


This bug was cloned from Perl-RT, rt47030.

Email addresses have have been truncated.

Id: 	47030
Status: 	resolved
Left: 	0 min
Queue: 	Verilog-Perl
Owner: 	Nobody
Requestors: 	MAREKR <Marek.Rouchal@>

Severity: 	Important
Broken in: 	3.210
X Attachments
Verilog-Perl-patch.diff

     * Wed Jun 17 03:08:05 2009 (513b) by MAREKR

Wed Jun 17 03:08:05 2009 MAREKR - Ticket created

Subject: 	adapt Verilog::Getopt to recent releases of Getopt::Long

Recent versions of Getopt::Long return objects - this causes failures in
the test of SystemPerl. The root cause is a
if(ref $_[0])
in Verilog::Getopt line 227, which is true for the
Getopt::Long::Callback object. It seems to work OK if we test for ref
and check whether the reference is an ARRAY. See the attached patch.

-Marek

Subject: 	Verilog-Perl-patch.diff

[application/octet-stream 513b]
Message body not shown because it is too large or is not plain text.

Wed Jun 17 08:04:02 2009 WSNYDER - Correspondence added

Fixed in 3.211 that's being uploaded now.

Thanks much for sending in a patch!

Wed Jun 17 08:04:03 2009 RT_System - Status changed from 'new' to 'open'

Wed Jun 17 08:04:04 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
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.