AaronBallman wrote: > I'd be oppose to try to invent what would effectively be yet another string > semantics for this. However, there maybe a spec bug here Presumably the > intent of the feature is to allow header-names and so maybe the syntax should > be that of and header-name?
That could be a reasonable idea; do line directives support a `<path/to/file>` form as well as a quoted form? > The two options are > > * status quo, these things are strings and invalid escape sequences > should be diagnose - because `\` would be interpreted as escape sequences > > * these things are header names and `\` is always just a `\`. > > > I mean, consider `#line 1 "C:\test"` - that does not do what you think it > does https://godbolt.org/z/EhKnere7v LOL but what if I want my terminal to "ding" on diagnostics by using a bell character? ;-) I don't have a strong opinion beyond "let's try to minimize disruption for users", so we could also allow this to be downgraded from an error back into a warning, potentially. https://github.com/llvm/llvm-project/pull/201413 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
