Gossamer Forum
(Advanced Search)
for
Home : Products : Gossamer Links : Discussions :

Ambiguous call error:

Dec 18, 2001, 3:19 PM
Eraser
Enthusiast (619 posts)
Dec 18, 2001, 3:19 PM
Post #1 of 4
Views: 1785
Shortcut
Quote Reply
Ambiguous call error:
I understand this error message is do to with an older version of perl complaining:

"Ambiguous call resolved as CORE::warn(), qualify as such or use & at GT::Base::error line 93"

Has Links SQL 2.1 been tweaked to deal with this issue? I'm running 2.05.

Thanks.

~ ERASER

Free JavaScripts @ Insight Eye
Dec 18, 2001, 3:34 PM
Paul
Veteran (19537 posts)
Dec 18, 2001, 3:34 PM
Post #2 of 4
Views: 1721
Shortcut
Quote Reply
Re: [Eraser] Ambiguous call error: In reply to
Supposedly that type of error doesn't cause any execution problems, it is just irritating I guess.

On line 93 I see a comment for sub AUTOLOAD

# We use autoload to provide an accessor/setter for all
# attributes. <-
Dec 18, 2001, 3:42 PM
Eraser
Enthusiast (619 posts)
Dec 18, 2001, 3:42 PM
Post #3 of 4
Views: 1723
Shortcut
Quote Reply
Re: [PaulW] Ambiguous call error: In reply to
Not really a big issue as no problems are present despite the message.

I thought this had been dealt with in earlier releases though, but obviously not.

~ ERASER

Free JavaScripts @ Insight Eye
Dec 18, 2001, 4:50 PM
Alex
Administrator (9387 posts)
Dec 18, 2001, 4:50 PM
Post #4 of 4
Views: 1715
Shortcut
Quote Reply
Re: [Eraser] Ambiguous call error: In reply to
Hi,

2.1 has silenced the error. All you need to do is look in GT::Base for anywhere that calls warn, and replace it with CORE::warn if you want to silence it.

Cheers,

Alex
--
Gossamer Threads Inc.