Menu
I have a templating system that looks similar to old-style ASP code. I run this through a class that rewrites the entire thing into C# source code, compiles, and finally executes it.
What I'm wondering is if there is some kind of #pragma-like directive I can sprinkle the generated C# code with that will make compile errors match the line numbers in my template file?
For instance, let's say I have this first and only line in my template code:
Object o = datta; // should be data, compiler error
but then in order to compile this I must add a namespace, a class, a method, and some boiler-plate code to it, so this line above, which is line #1 in my template file, actually ends up being line #17 (random number, just for illustrative purposes) in the C# code. The compiler error will naturally flag my error as being on line #17, and not on line #1.
I remember from another programming language I've used before (though I can't remember which one) that it had a directive that I could add, which would make error line numbers line up.
Is there any such thing in C# 3.5?
644
Which One Should You Use: Is There A or Is There Any? We must use 'a' with singular countable nouns and 'any' with uncountable nouns. We use 'is' with both singular countable nouns and uncountable nouns. Remember, uncountable nouns do have countable forms of measurement.
Use there is when the noun is singular (“There is a cat”). Use there are when the noun is plural (“There are two cats”).
Summary. Any may be used as a singular or a plural pronoun, depending on whether it refers to “at least one” or “one or more.” You may use either a singular verb like is or a plural verb like are with any (although use of the plural is more common).
Use “there is" when the noun is singular. Water is uncountable. So “Is there any water?” is the correct answer.
You have the #line preprocessor directive.
#linelets you modify the compiler's line number and (optionally) the file name output for errors and warnings.The
#line directivemight be used in an automated, intermediate step in the build process. For example, if lines were removed from the original source code file, but you still wanted the compiler to generate output based on the original line numbering in the file, you could remove lines and then simulate the original line numbering with#line.The
#line hiddendirective hides the successive lines from the debugger, such that when the developer steps through the code, any lines between a#line hiddenand the next#linedirective (assuming that it is not another #line hidden directive) will be stepped over. This option can also be used to allow ASP.NET to differentiate between user-defined and machine-generated code. Although ASP.NET is the primary consumer of this feature, it is likely that more source generators will make use of it.A
#line hiddendirective does not affect file names or line numbers in error reporting. That is, if an error is encountered in a hidden block, the compiler will report the current file name and line number of the error.The
#line filenamedirective specifies the file name you want to appear in the compiler output. By default, the actual name of the source code file is used. The file name must be in double quotation marks ("") and must be preceded by a line number.
192
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
