You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Kevin Ballard (JIRA)" <ji...@apache.org> on 2008/06/24 01:37:45 UTC
[jira] Created: (THRIFT-50) Deprecated classes blow up if
Object.inherited has been redefined to call a method on the new class
Deprecated classes blow up if Object.inherited has been redefined to call a method on the new class
---------------------------------------------------------------------------------------------------
Key: THRIFT-50
URL: https://issues.apache.org/jira/browse/THRIFT-50
Project: Thrift
Issue Type: Bug
Components: Library (Ruby)
Reporter: Kevin Ballard
Attachments: 0001-rb-Fix-the-deprecation-stuff-to-work-when-an-inject.patch
When Object.inherited calls a method on the newly-defined class (such as in ActiveSupport 1.4.3), the deprecation stuff blows up because it accesses a value that hasn't been set yet. The attached patch fixes this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (THRIFT-50) Deprecated classes blow up if
Object.inherited has been redefined to call a method on the new class
Posted by "Kevin Clark (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/THRIFT-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on THRIFT-50 started by Kevin Clark.
> Deprecated classes blow up if Object.inherited has been redefined to call a method on the new class
> ---------------------------------------------------------------------------------------------------
>
> Key: THRIFT-50
> URL: https://issues.apache.org/jira/browse/THRIFT-50
> Project: Thrift
> Issue Type: Bug
> Components: Library (Ruby)
> Reporter: Kevin Ballard
> Assignee: Kevin Clark
> Attachments: 0001-rb-Fix-the-deprecation-stuff-to-work-when-an-inject.patch
>
>
> When Object.inherited calls a method on the newly-defined class (such as in ActiveSupport 1.4.3), the deprecation stuff blows up because it accesses a value that hasn't been set yet. The attached patch fixes this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (THRIFT-50) Deprecated classes blow up if
Object.inherited has been redefined to call a method on the new class
Posted by "Kevin Ballard (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/THRIFT-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Ballard updated THRIFT-50:
--------------------------------
Attachment: 0001-rb-Fix-the-deprecation-stuff-to-work-when-an-inject.patch
> Deprecated classes blow up if Object.inherited has been redefined to call a method on the new class
> ---------------------------------------------------------------------------------------------------
>
> Key: THRIFT-50
> URL: https://issues.apache.org/jira/browse/THRIFT-50
> Project: Thrift
> Issue Type: Bug
> Components: Library (Ruby)
> Reporter: Kevin Ballard
> Attachments: 0001-rb-Fix-the-deprecation-stuff-to-work-when-an-inject.patch
>
>
> When Object.inherited calls a method on the newly-defined class (such as in ActiveSupport 1.4.3), the deprecation stuff blows up because it accesses a value that hasn't been set yet. The attached patch fixes this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (THRIFT-50) Deprecated classes blow up if
Object.inherited has been redefined to call a method on the new class
Posted by "Kevin Clark (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/THRIFT-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Clark reassigned THRIFT-50:
---------------------------------
Assignee: Kevin Clark
> Deprecated classes blow up if Object.inherited has been redefined to call a method on the new class
> ---------------------------------------------------------------------------------------------------
>
> Key: THRIFT-50
> URL: https://issues.apache.org/jira/browse/THRIFT-50
> Project: Thrift
> Issue Type: Bug
> Components: Library (Ruby)
> Reporter: Kevin Ballard
> Assignee: Kevin Clark
> Attachments: 0001-rb-Fix-the-deprecation-stuff-to-work-when-an-inject.patch
>
>
> When Object.inherited calls a method on the newly-defined class (such as in ActiveSupport 1.4.3), the deprecation stuff blows up because it accesses a value that hasn't been set yet. The attached patch fixes this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (THRIFT-50) Deprecated classes blow up if
Object.inherited has been redefined to call a method on the new class
Posted by "Kevin Clark (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/THRIFT-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Clark closed THRIFT-50.
-----------------------------
Resolution: Fixed
In commit 670976. Thanks!
> Deprecated classes blow up if Object.inherited has been redefined to call a method on the new class
> ---------------------------------------------------------------------------------------------------
>
> Key: THRIFT-50
> URL: https://issues.apache.org/jira/browse/THRIFT-50
> Project: Thrift
> Issue Type: Bug
> Components: Library (Ruby)
> Reporter: Kevin Ballard
> Assignee: Kevin Clark
> Attachments: 0001-rb-Fix-the-deprecation-stuff-to-work-when-an-inject.patch
>
>
> When Object.inherited calls a method on the newly-defined class (such as in ActiveSupport 1.4.3), the deprecation stuff blows up because it accesses a value that hasn't been set yet. The attached patch fixes this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (THRIFT-50) Deprecated classes blow up if
Object.inherited has been redefined to call a method on the new class
Posted by "Kevin Ballard (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/THRIFT-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Ballard updated THRIFT-50:
--------------------------------
Attachment: 0001-rb-Fix-the-deprecation-stuff-to-work-when-an-inject.patch
New version of the patch to turn off warnings in the context of Object.inherited
> Deprecated classes blow up if Object.inherited has been redefined to call a method on the new class
> ---------------------------------------------------------------------------------------------------
>
> Key: THRIFT-50
> URL: https://issues.apache.org/jira/browse/THRIFT-50
> Project: Thrift
> Issue Type: Bug
> Components: Library (Ruby)
> Reporter: Kevin Ballard
> Assignee: Kevin Clark
> Attachments: 0001-rb-Fix-the-deprecation-stuff-to-work-when-an-inject.patch
>
>
> When Object.inherited calls a method on the newly-defined class (such as in ActiveSupport 1.4.3), the deprecation stuff blows up because it accesses a value that hasn't been set yet. The attached patch fixes this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (THRIFT-50) Deprecated classes blow up if
Object.inherited has been redefined to call a method on the new class
Posted by "Kevin Ballard (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/THRIFT-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Ballard updated THRIFT-50:
--------------------------------
Attachment: (was: 0001-rb-Fix-the-deprecation-stuff-to-work-when-an-inject.patch)
> Deprecated classes blow up if Object.inherited has been redefined to call a method on the new class
> ---------------------------------------------------------------------------------------------------
>
> Key: THRIFT-50
> URL: https://issues.apache.org/jira/browse/THRIFT-50
> Project: Thrift
> Issue Type: Bug
> Components: Library (Ruby)
> Reporter: Kevin Ballard
> Assignee: Kevin Clark
> Attachments: 0001-rb-Fix-the-deprecation-stuff-to-work-when-an-inject.patch
>
>
> When Object.inherited calls a method on the newly-defined class (such as in ActiveSupport 1.4.3), the deprecation stuff blows up because it accesses a value that hasn't been set yet. The attached patch fixes this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.