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

Updated build/lisp.tcl to not specify FN2 for those lisp compilations #1092

Merged
merged 1 commit into from
Jul 22, 2018

Conversation

eswenson1
Copy link
Member

where the default of > would be more appropriate. This fixes, in
particular the incorrect compilation of LIBDOC; TIME KMP8 instead of
LIBDOC; TIME KMP9. Resolves #1091.

where the default of > would be more appropriate. This fixes, in
particular the incorrect compilation of LIBDOC; TIME KMP8 instead of
LIBDOC; TIME KMP9. Resolves #1091.
Copy link
Contributor

@atsampson atsampson left a comment

Choose a reason for hiding this comment

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

Looks good.

I guess the only reason not to use > would be if we had multiple versions where > wouldn't pick the right one - but for all of these (except TIME) we've only got one version anyway.

@eswenson1
Copy link
Member Author

Yes. There have been times when the next version of a libdoc source changed authors and versions, and where > would do the wrong thing in the face of both versions. But that doesn’t apply here.

On the other hand, it isn’t clear to me that this version of LIBDOC; TIME KMP8 should be called that since KMP didn’t make the change. We probably should have used yours or my initials. Had we used mine, that issue would have arisen since KMP8 is > EJS9!

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

Successfully merging this pull request may close these issues.

lisp.tcl builds wrong version of LIBDOC; TIME
2 participants