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

outer classes/methods should not be encoded #4

Closed
Antoine321 opened this issue Dec 8, 2015 · 2 comments
Closed

outer classes/methods should not be encoded #4

Antoine321 opened this issue Dec 8, 2015 · 2 comments

Comments

@Antoine321
Copy link

example:

  • new stdClass() : should not be encoded as it's not declared in the source folder (it's a standard class)
  • DomDocument::{whatever constant} : should not be encoded, as the DomDocument class is not declared in the source folder (standard class)

Until that is resolved, I have to deactivate obfuscation for classes and methods.
Well, I know it's minor glitches, overall good job !

@pk-fr
Copy link
Owner

pk-fr commented Dec 8, 2015

Thank's for having tested it!
You're absolutly right!!!
I've forgotten predefined classes .... as well as predefined interfaces (there is no predefined traits yet)
I will correct it as soon as I have some time
I will release a new version next week-end If I do not find any time before.
I hope you will star this project afterwards...
Best regards,
Pascal

@pk-fr
Copy link
Owner

pk-fr commented Dec 12, 2015

Hi Antoine,

I just published 1.8.0 release
a new config file $conf->t_ignore_pre_defined_classes element, replaces the old $conf->t_ignore_module_methods.

all pre-defined classes, class constants, properties, and methods are now not obfuscated by default.

Cheers,
Pascal

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