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

ADLB_i1 callbacks switch to wrong namespace? #80

Closed
mstovenour opened this issue Feb 16, 2013 · 6 comments
Closed

ADLB_i1 callbacks switch to wrong namespace? #80

mstovenour opened this issue Feb 16, 2013 · 6 comments
Labels

Comments

@mstovenour
Copy link
Collaborator

I noticed that several of the ALDB_i1 functions switch to the AllLinkDataBase namespace once the call backs are completed. Honestly I don't fully understand the implications. Is this the correct behavior or should all the ALDB_i1 functions switch back to the ALDB_i1 namespace?
Example (1 of 3)
sub delete_link
....
package main;
eval($link_parms{callback});
package Insteon::AllLinkDataBase;

@krkeegan
Copy link
Collaborator

I don't think there is any legitimate reason for this, I am 99% sure this
is a typo. Things continue to work fine because MH doesn't make use of
namespace variables very much. Almost all of the variables are saved
within an object.

On Sat, Feb 16, 2013 at 11:58 AM, Michael Stovenour <
notifications@github.com> wrote:

I noticed that several of the ALDB_i1 functions switch to the
AllLinkDataBase namespace once the call backs are completed. Honestly I
don't fully understand the implications. Is this the correct behavior or
should all the ALDB_i1 functions switch back to the ALDB_i1 namespace?
Example (1 of 3)
sub delete_link
....
package main;
eval($link_parms{callback});
package Insteon::AllLinkDataBase;


Reply to this email directly or view it on GitHubhttps://github.com//issues/80.

@mstovenour
Copy link
Collaborator Author

OK, I can clean it up later when consolidating the i1 and i2 code. If anyone decides to look into issue (#57) then this should probably be cleaned up as part of that work before doing a lot of testing.

@krkeegan
Copy link
Collaborator

Pull #69 fixed known issues of this.

@mstovenour
Copy link
Collaborator Author

There are multiple instances of this in Insteon::ALDB_i1 That's where I first noticed it.

@mstovenour mstovenour reopened this Feb 26, 2013
@krkeegan
Copy link
Collaborator

Can we call this closed? We seem to have tackled all of the known ones.

@mstovenour
Copy link
Collaborator Author

I think we have this one covered

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

No branches or pull requests

2 participants