Talk:UTIL VarArgs: Difference between revisions
		
		
		
		
		
		Jump to navigation
		Jump to search
		
				
		
		
	
| No edit summary | Biohazard 90 (talk | contribs)  No edit summary | ||
| Line 1: | Line 1: | ||
| Why would you ever want to use VarArgs over say [[V_vsnprintf]]? --[[User:DaFox|DaFox]] 05:49, 12 April 2011 (UTC) | Why would you ever want to use VarArgs over say [[V_vsnprintf]]? --[[User:DaFox|DaFox]] 05:49, 12 April 2011 (UTC) | ||
| :Cause VarArgs is documented and [[V_vsnprintf]] isn't. ;) [[User:LordNed|LordNed]] 06:01, 12 April 2011 (UTC) | :Cause VarArgs is documented and [[V_vsnprintf]] isn't. ;) [[User:LordNed|LordNed]] 06:01, 12 April 2011 (UTC) | ||
| ::V_vsnprintf still requires you to allocate memory for the output while (UTIL_)VarArgs simply dumps everything into a static array and returns a pointer. Way more convenient to use in many cases... --[[User:Biohazard 90|Biohazard]] 12:01, 12 April 2011 (UTC) | |||
Latest revision as of 05:01, 12 April 2011
Why would you ever want to use VarArgs over say V_vsnprintf? --DaFox 05:49, 12 April 2011 (UTC)
- Cause VarArgs is documented and V_vsnprintf isn't. ;) LordNed 06:01, 12 April 2011 (UTC)
- V_vsnprintf still requires you to allocate memory for the output while (UTIL_)VarArgs simply dumps everything into a static array and returns a pointer. Way more convenient to use in many cases... --Biohazard 12:01, 12 April 2011 (UTC)