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

Correct spelling of daemon. #535

Merged
merged 2 commits into from Jul 11, 2018
Merged

Correct spelling of daemon. #535

merged 2 commits into from Jul 11, 2018

Conversation

sbleon
Copy link
Contributor

@sbleon sbleon commented Jul 6, 2018

"deamon" is a misspelling, and should not be considered valid.

Copy link
Contributor

@isapir isapir left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sbleon I agree with you, but unfortunately "APIs are forever", or at least for a very long time, and the change in core/src/main/java/lucee/runtime/tag/ThreadTag.java might break someone's code and 5.3 is already in beta.

We can put a // FUTURE remove "deamon" comment, which we usually check before working on a new version, so that we can remove it in the future.

@sbleon
Copy link
Contributor Author

sbleon commented Jul 11, 2018

Sounds good, Igal. I thought that daemon threads were a brand new feature in 5.3, but now I see that they've been around for 3 years! I agree that breaking changes should be avoided.

Do you know if there's a deprecation warning mechanism in Lucee? That would be a nice thing to have, but I couldn't find anything with a quick search.

@isapir
Copy link
Contributor

isapir commented Jul 11, 2018

@sbleon Unfortunately there is no formal process in place for deprecation. We have discussed it many times but nothing concrete came of that. We should definitely set one up though, I agree.

@isapir isapir merged commit e048bef into lucee:5.3 Jul 11, 2018
@bdw429s
Copy link
Contributor

bdw429s commented Jul 11, 2018

Usually when you ask the community about deprecating anything, the only response you get is "Wait, you can't remove anything!!" :)

@isapir
Copy link
Contributor

isapir commented Jul 11, 2018

Right, which is nonsensical if you ask me.

Major versions may have breaking changes IMO, though Removal should be preceded by Deprecation first, so at least 2 major versions to remove.

Python is the best example for a language that came back from the dead, and Python 3 is completely incompatible with Python 2. If they can do that, then I don't see why we can't.

It will make the code cleaner and in some cases even faster, e.g. why test for a misspelled word like deamon in future versions?

@isapir
Copy link
Contributor

isapir commented Jul 11, 2018

Having said that here... If you want to continue this discussion then let's, at the risk of starting WW3, do it in dev.lucee.org ;)

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