[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[cdt-dev] [Launch] Why do CDT launch configs map the project?
|
Hello, CDT launch experts,
Why do the CDT launch configurations commonly set the context project as the "mapped resource" for the config? I ask for two reasons:
- this is different from JDT, which never sets mapped resources in its launch configs (bad JDT, perhaps?)
- it results in launch configs being filtered out of the dialog if either the user sets the project name to a non-existent project or the project is temporarily unavailable (it is surprising to users to see them disappear)
One can argue that users should not be permitted to type non-existent project names into these configs, but JDT allows it (you just can't launch) and a validation problem is shown, so it's nice to let users save their bad data anyway. Besides that there are any number of ways to get a bad project name after the fact.
Anyhow, the real gist of my question is what would be the impact of omitting the resource mapping either
- always (to what extent does CDT rely on it? CDT never queries the mapped resources of a config), or
- when the user enters a non-existent project name (some call sites in the CDT code already check for project existence before setting the mapped resources, but not all)
What is the committers' opinion of changing how the resource mappings are set? Any preference?
Thanks,
Christian
