Skip to content

Conversation

@MisterDA
Copy link
Contributor

An invocation such as ocamlc (without any command-line parameters), or ocamlc -o a.out will now fail with an error message and an error code.

cc @shindere who reviewed the PR offline
fixes #12497

@shindere
Copy link
Contributor

shindere commented Sep 28, 2023 via email

@damiendoligez damiendoligez self-assigned this Oct 4, 2023
An invocation such as `ocamlc` (without any command-line parameters),
or `ocamlc -o a.out` will now fail with an error message and an error
code.
@MisterDA
Copy link
Contributor Author

MisterDA commented Oct 4, 2023

Rebased to fix conflicts in Changes.

@shindere
Copy link
Contributor

shindere commented Oct 4, 2023

This has been discussed in triaging meeting and it has been agreed that
the behaviour of failing when no input file is provided is what we want, even
when no -o foo option is specified.

This PR should be good to go once it has been rebased to solve the conflict
in Changes.

@xavierleroy
Copy link
Contributor

As discussed during today's triage meeting: the "no input files" error behavior looks good, that's what GCC, Clang and CompCert do.

@emillon
Copy link
Contributor

emillon commented Jul 5, 2024

FYI, ocamlfind used to rely on the former behaviour: ocaml/ocamlfind#78

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Compiler behaviour on -o foo and no input files

6 participants