https://wiki.secondlife.com/w/api.php?action=feedcontributions&feedformat=atom&user=Trek+Houston 2026-07-28T06:49:40Z User contributions MediaWiki 1.42.1 https://wiki.secondlife.com/w/index.php?title=Talk:Coding_standard&diff=5892 2007-01-20T02:27:32Z

<p>Trek Houston: OpenBSD and other os&#039;s vs coding standard...</p> <hr /> <div>== Indentation ==<br /> <br /> What does it mean ''Use 4 character tabs for indentation and ensure that your editor is not converting tabs to spaces.''?<br /> <br /> If my editor doesn't change tabs to spaces, what's the difference whether they are shown in my editor as 4, 8 or 13 spaces?<br /> <br /> [[User:Tharkang Varayez|Tharkang Varayez]] 09:18, 8 January 2007 (PST)<br /> <br /> :Non-code-structure spacing. Consider:<br /> func_call(one_param, two_param, three_param,<br /> four_param, five_param, six_param);<br /> :The indent under func_call could be either ten spaces, or two tabs and two spaces. --[[User:Carnildo Greenacre|Carnildo Greenacre]] 21:33, 10 January 2007 (PST)<br /> <br /> == OpenBSD and other os's? ==<br /> <br /> The coding standard says LL_WINDOWS, LL_DARWIN, LL_LINUX are the only acceptable ifdef items. I have a diff that makes OpenBSD work, and sofar I've used __OpenBSD__ because c or c++ compilers on OpenBSD always define this. What does this mean for other operating systems as well? Can the coding standard be made more flexible in this regard? I know I could change it, but I'd rather get some idea that I'm changing it to say the desired thing from Linden Lab's point of view.</div>

Trek Houston