ScratchMonkey wrote:
And the latter would be wrong, as you should never optimize until you know
where the bottlenecks are. Otherwise you're wasting programmer time.
Especially when you consider that the workaround is to pull a file *from
another server* via URL, which is grossly more pessimal.
This looks like some junior programmer was using an array on the stack
instead of a string class (which would grow to accomodate any size). Very
bad style for production code. And generally not needed even in a quick
test hack, given the availability of good string classes in almost any
framework.
I agree.
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
