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

Don't use .o at the end of executable file names #12

Open
cwant opened this issue Dec 18, 2018 · 1 comment
Open

Don't use .o at the end of executable file names #12

cwant opened this issue Dec 18, 2018 · 1 comment

Comments

@cwant
Copy link

cwant commented Dec 18, 2018

A lot of the examples create executables with a .o at the end of the file names, e.g.,

chpl --fast hello.chpl -o hello.o

Having an executable file with an extension .o defies the typical convention of .o files (an object file: compiled but unlinked code, which can't be executed on its own).

I would recommend (and am willing to do the work) to change the examples, for example replacing the above example with:

chpl --fast hello.chpl -o hello
@razoumov
Copy link
Member

Hi Chris. Good idea! There are actually quite a lot of things I would like to edit in this repository. For example, there are lots of inconsistencies between the task-parallel and domain-parallel parts. However, I am the only maintainer, and HPC Carpentry set up the repository in such a way that any pull request needs to be approved before merging. As you can see, I submitted a pull request in September, ironically listing maintainers, and I still can't merge it, as I am the only maintainer, and the request needs an approving review. If you agree, please join as a maintainer, so that we could really edit these lessons. Thanks!

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