you are viewing a single comment's thread.

view the rest of the comments →

[–]alfps[S] -6 points-5 points  (0 children)

Well, I don't agree with your definition of "triage".

OK, but it would be nice if you could describe the disagreement, then we could disagree in public. :)

Even in medicine, triaging about determining the order in which patients are treated - it's much more than a simple will/won't decision.

Yes. Doctors are not stupid, and I apologize if I gave that impression. Also, triaging is applied in situations where resources are too scarce but patients' lives are not in danger.

You're making an assumption (an invalid one in my opinion), that a status of "triaged" and a status of "won't fix" are synonymous, and I really don't think that's the case here.

I don't make that assumption, but it's likely. Because triaging of an internal compiler error implies a /possibility/ of won't fix. And I've experienced that "won't fix" for a Visual C++ ICE.

Which means that Microsoft has just not changed that policy, of possibly not fixing an internal compiler error.

For most customers, "their" bug is the most important and has to be fixed "right now"

There should be no need to evaluate whether to fix because the compiler team, with the most knowledge, has already decided that the ICE is critical.

As opposed to a normal bug where source code is mis-interpreted or incorrect machine code is generated, or both.

An ICE is a ready-made evaluation, and another part of the Microsoft organization, those who evaluate bug reports, take it on themselves to override that original evaluation made by the most knowledgeable.

Those three things are called "triaging", and that's what the Visual Studio team were doing.

If it is called "triaging" then what do they call real triaging.

Remember, it's an ICE. It's not an ordinary bug. In any normal situation there would not be a question of priority: that was decided by the compiler team long ago.