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

1 <!--
4 SPDX-License-Identifier: curl
5 -->
11 single code base. Easy-to-read is an important property of code and helps
17 Our C code has a few style rules. Most of them are verified and upheld by the
19 by the build system when built after `./configure --enable-debug` has been
24 particularly unusual rules in our set of rules.
26 We also work hard on writing code that are warning-free on all the major
28 causes warnings is not accepted as-is.
32 Try using a non-confusing naming scheme for your new functions and variable
35 understandable and be named according to what they are used for. File-local
39 how we name non-exported library-global symbols.
73    next to each other in different windows. It allows two or three source
74    code windows next to each other on the same screen - as well as multiple
75    terminal and debugging windows.
89 You may omit the braces if they would contain only a one-line statement:
184 [], ->, ., ++, --** and Unary **+, -, !, ~, &** operators excluded they should
194 size += -2 + 3 * (a + b);
195 ptr->member = a++;
196 struct.field = b--;
229 If a continuation line is part of an expression or sub-expression then you
232 cases follow the 2-space indent guideline. Here are some examples from
236 if(Curl_pipeline_wanted(handle->multi, CURLPIPE_HTTP1) &&
237    (handle->set.httpversion != CURL_HTTP_VERSION_1_0) &&
238    (handle->set.httpreq == HTTPREQ_GET ||
239     handle->set.httpreq == HTTPREQ_HEAD))
247 data->set.http_disable_hostname_check_before_authentication =
274 shall be generated by the configure script for unix-like systems and they are
275 hard-coded in the `config-[system].h` files for the others.
280 depending on a build-time conditional: