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

shadow members from 3rd party libs... #73

Open
TurkeyMan opened this issue Aug 18, 2014 · 2 comments
Open

shadow members from 3rd party libs... #73

TurkeyMan opened this issue Aug 18, 2014 · 2 comments

Comments

@TurkeyMan
Copy link
Contributor

So the idea is to use @noscript to control things that should be hidden from script, this is obvious I think, but how can we assert such control over 3rd party libs?

Thing is, the metatable is created first time a value is pushed... but we want to influence the creation of the metatable for some particular 3rd party type.
We'll need some sort of pre-registration function I think which can pre-create the metatable, where we can supply a type, and also a member shadow list or something.

Thoughts? (I just opened this issue to keep thoughts/plans in a public place)

@JakobOvrum
Copy link
Owner

I think I intended registerType to do this job, but I got side-tracked by working on pushing the static interface. Maybe the same function can be overloaded to take a filter function which spits out a bool given a fully qualified identifier? It can all be done at compile-time.

The intention is to add support for pushing entire modules automatically, so this is relevant for that too.

@TurkeyMan
Copy link
Contributor Author

Okay, good approach. I'll keep this in mind.

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