Difference between revisions of "Talk:Coding standard"

From Second Life Wiki
Jump to navigation Jump to search
(OpenBSD and other os's vs coding standard...)
Line 11: Line 11:
                     four_param, five_param, six_param);
                     four_param, five_param, six_param);
: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)
: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)
== OpenBSD and other os's? ==
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.

Revision as of 18:27, 19 January 2007

Indentation

What does it mean Use 4 character tabs for indentation and ensure that your editor is not converting tabs to spaces.?

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?

Tharkang Varayez 09:18, 8 January 2007 (PST)

Non-code-structure spacing. Consider:
         func_call(one_param, two_param, three_param,
                   four_param, five_param, six_param);
The indent under func_call could be either ten spaces, or two tabs and two spaces. --Carnildo Greenacre 21:33, 10 January 2007 (PST)

OpenBSD and other os's?

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.