|
|
> The above would be a nice feature for fluid to better follow up with
> compiler output.
Maybe so - but if it were possible, I wonder how we might make a system so that a user can get from a compiler error, back to a specific entity in fluid...
E.g. if the compiler throws an error saying "some obscure error at line 234 in file foo.cxx", can we add preprocessor directives, or etc., so that the error message would state which actual widget the error occured in.
How portable is the "#line" directive?
I'm thinking that the fluid generated code be peppered with #line directives at the start or each entity (for some value of entity...) like this
#line 228 "get_method : some_widget : foo.cxx"
Then when the error happens, the compiler says:
some obscure error at line 234 in file get_method : some_widget : foo.cxx
Or something...
But probably not.
--
Ian
[ Direct Link to Message ] | |
|
| |