On Sun, Apr 24, 2011 at 9:47 PM, buginator wrote:
> In short, we have asserts that fire, and we *know* there is a issue,
> but can't get at that issue for multiple reasons. No need to spam the
> in-game console with assert messages.
Then stop sending LOG_ERROR to the console?
Perhaps make a new
On 4/24/11, Per Inge Mathisen wrote:
> On Sun, Apr 24, 2011 at 6:36 AM, buginator wrote:
>> Unless there are any objections, I plan to demote ASSERT_FAILURE() to
>> use LOG_INFO instead of LOG_ERROR.
>>
>> The main reason for this is that LOG_ERROR is meant for serious
>> errors, and all LOG_ERRO
On Sun, Apr 24, 2011 at 6:36 AM, buginator wrote:
> Unless there are any objections, I plan to demote ASSERT_FAILURE() to
> use LOG_INFO instead of LOG_ERROR.
>
> The main reason for this is that LOG_ERROR is meant for serious
> errors, and all LOG_ERRORs are echoed to the in game console on all
>
24.04.2011 06:36, buginator wrote:
> Unless there are any objections, I plan to demote ASSERT_FAILURE() to
> use LOG_INFO instead of LOG_ERROR.
>
> The main reason for this is that LOG_ERROR is meant for serious
> errors, and all LOG_ERRORs are echoed to the in game console on all
> platforms.
> L
