There is no warning for this AFAIK. But would removing the following from the Penetrating cold self warning work?
Or are more interested in this, and do you think it's worth adding it as additional warning?
- We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil. Yet we should not pass up our opportunities in that critical 3%.A good programmer will not be lulled into complacency by such reasoning, he will be wise to look carefully at the critical code; but only after that code has been identified - Donald Knuth
- Bottlenecks occur in surprising places, so don't try to second guess and put in a speed hack until you have proven that's where the bottleneck is. - Rob Pike
- The First Rule of Program Optimization: Don't do it. The Second Rule of Program Optimization (for experts only!): Don't do it yet. - Michael A. Jackson
acegui:RegisterLayout("Custom_Layout", function(content, children) children:SetWidth(content:GetWidth() or 0) children.frame:SetPoint("TOPLEFT",content,"TOPLEFT",0,0) children.frame:Show() safecall( content.obj.LayoutFinished, content.obj, nil, 100 ) end ) frame:SetLayout("Custom_Layout")
Quote from AdirelleMy statement had no error. You misunderstood what I meant.
Quote from StarousczAnd why is using AceComm bad idea? I thought it would be bad idea not to recieved it with acecomm when i use acecomm in raidvoice to broadcast?
P.S. I am a Java programmer i hate C :)