Talk:Compiler errors overview

Errors format

I thought of changing the format of errors, because it kinda looked like everything's floating. Here's the table format I thought of:

Error	Message
#0001	Unexpected 'defaultproperties'
This seems to occur when you have an end of multi-comment preceded by a line comment on the same line. See Compiler issues. Keep in mind that you can not specify default properties in code while using the UnrealEd internal script editor. Doing so will give you this error as well. To change the default properties of a class in UnrealEd, you need to type editdefault class=classname in the command line of the editor. Correct and Wrong example Correct Wrong /* The quick brown fox jumps over the lazy dog */ // ... /* The quick brown fox jumps over the lazy dog */ // ...

As you see i did give the error an number for reference purpose. Please let me know your opinions, also if you will use it then make sure you turn it into a template instead to avoid duplicating so much code. The colors might need some work hehe :P --Eliot 02:52, 10 November 2010 (UTC)

The colors need indeed some work. I imagine it hard to read through it if it's formatted this way because it will have always three sections per error and then does it start again. It would probably help if the background color of an error alternates between grey and white (or a brighter grey) for each error so that you can better distinguish sections.

And since the number doesn't have any hard reference (unless they are in fact internally numbered by the compiler) and is rather unofficial, it shouldn't be at the left of the box but rather discretely added at the back because most people won't use it. Or leave it completely away. :>

Another thing I was wondering about was to get a uniform format for stuff. If we have varying stuff in the compiler message, should we use function or FUNCTION? The current inconsistency doesn't look that nice. --Crusha 21:49, 18 December 2010 (UTC)

Error duplicates

Thats defiantly the way the compiler spat it out at me for the Mismatch error, Im not sure but maybe it was changed in some engine versions or it is infact a different error code for virtually the same thing. I usually just put em up as I find em in no particular test order or related to any version in specific so its possible that one was put up when I first started with an older version of UDK.

In regards to the duplicate on the operator mismatch one is special case in an if statement its not actually always a missing expression but it can be incorrect operator when someone might have wanted to use '&&'. For eg if(foo+bar){//dostuff} pretty sure that was why I put it up. --00zX 02:11, 1 December 2010 (UTC)