Lines Matching +full:windows +full:- +full:build +full:- +full:rules

5 single code base. Easy-to-read is an important property of code and helps
11 Our C code has a few style rules. Most of them are verified and upheld by the
13 by the build system when built after `./configure --enable-debug` has been
18 particularly unusual rules in our set of rules.
20 We also work hard on writing code that are warning-free on all the major
22 will cause warnings will not be accepted as-is.
26 Try using a non-confusing naming scheme for your new functions and variable
29 understandable and be named according to what they are used for. File-local
33 how we name non-exported library-global symbols.
67    next to each other in different windows. It allows two or three source
68    code windows next to each other on the same screen - as well as multiple
69    terminal and debugging windows.
83 You may omit the braces if they would contain only a one-line statement:
178 [], ->, ., ++, --** and Unary **+, -, !, ~, &** operators excluded they should
188 size += -2 + 3 * (a + b);
189 ptr->member = a++;
190 struct.field = b--;
223 If a continuation line is part of an expression or sub-expression then you
226 cases follow the 2-space indent guideline. Here are some examples from
230 if(Curl_pipeline_wanted(handle->multi, CURLPIPE_HTTP1) &&
231    (handle->set.httpversion != CURL_HTTP_VERSION_1_0) &&
232    (handle->set.httpreq == HTTPREQ_GET ||
233     handle->set.httpreq == HTTPREQ_HEAD))
241 data->set.http_disable_hostname_check_before_authentication =
268 shall be generated by the configure script for unix-like systems and they are
269 hard-coded in the `config-[system].h` files for the others.
274 depending on a build-time conditional: