Skip to content

Conversation

@br4sco
Copy link
Contributor

@br4sco br4sco commented Nov 21, 2024

No description provided.

@marten-voorberg
Copy link
Contributor

Minor note on the naming here. Since we have print and printLn for outputing to stdout, should we maybe call this errorLn for consistency?

@br4sco
Copy link
Contributor Author

br4sco commented Dec 4, 2024

Minor note on the naming here. Since we have print and printLn for outputing to stdout, should we maybe call this errorLn for consistency?

We have an intrinsic error, which exists in a program with an error code (and a message). I named it printErrorLn because we have an intrinsic, printError, which prints a string to stderr without a newline without exiting the program (hence the same naming convention as print and printLn)

@david-broman david-broman merged commit 7253cc3 into miking-lang:develop Dec 5, 2024
2 checks passed
@br4sco br4sco deleted the print-err-ln branch December 5, 2024 18:10
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.

3 participants