Skip to content

Remove null reference exception when no JIT_DASM_ROOT specified.#6

Merged
russellhadley merged 1 commit into
dotnet:masterfrom
russellhadley:NoJitDasmRoot
Jun 27, 2016
Merged

Remove null reference exception when no JIT_DASM_ROOT specified.#6
russellhadley merged 1 commit into
dotnet:masterfrom
russellhadley:NoJitDasmRoot

Conversation

@russellhadley
Copy link
Copy Markdown
Contributor

Change adds a bit of a better error message and fixes a initialization problem
when computing the next "tag" when the output directory is empty.

Change adds a bit of a better error message and fixes a initialization problem
when computing the next "tag" when the output directory is empty.
@russellhadley
Copy link
Copy Markdown
Contributor Author

@AndyAyersMS @BruceForstall Fixes the issue with JIT_DASM_ROOT not specified.

@russellhadley
Copy link
Copy Markdown
Contributor Author

Fixes part 1 of issue #1

@AndyAyersMS
Copy link
Copy Markdown
Member

I think this does what I expect -- that the tool is usable via command line args even if JIT_DASM_ROOT is not set.

To confirm: is it an error if JIT_DASM_ROOT is not set, or is the app now just notifying you...?

@russellhadley
Copy link
Copy Markdown
Contributor Author

It is not an error if there is no JIT_DASM_ROOT, the message from the tool is just notification in case the user intends to have defaults via JIT_DASM_ROOT.

@AndyAyersMS
Copy link
Copy Markdown
Member

Good... changes LGTM.

@russellhadley russellhadley merged commit 78c2dd2 into dotnet:master Jun 27, 2016
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.

2 participants