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
A lot of the examples create executables with a
.oat the end of the file names, e.g.,Having an executable file with an extension
.odefies the typical convention of.ofiles (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: