Hi all,
I allways use this "" to break a long code line into two or more parts. I think that, in this way, the code is more readable. I’ve never had any problem with that and I didn’t know it was no neccesary with gcc. But, could some body tell me if there are compilation problems with that? In that case, I have to clean it.
Regards,
Roberto.
···
--
Roberto Antolín Sánchez
Politecnico di Milano – Polo Regionale di Como
(Laboratorio di Geomatica V2.8)
Via Valleggio, 11 – 22100 Como, Italy
tel: +39 031 332 7533 || fax: +39 031 332 7519
email: [roberto.antolin@polimi.it](mailto:roberto.antolin@polimi.it)
Roberto Antolin wrote:
>>C question re that fix: (vector/lidar/v.outlier/main.c)
>>
>> /* Structs' declarations */
>> struct Map_info In, Out, Outlier, Qgis;
>> struct Option *in_opt, *out_opt, *outlier_opt, *qgis_opt, *passoE_opt, *passoN_opt, \
>> *lambda_f_opt, *Thres_O_opt;
>>
>>
>>is the end of line "\" harmful or treated like whitespace?
I allways use this "\" to break a long code line into two or more parts.
I think that, in this way, the code is more readable. I've never had any
problem with that and I didn't know it was no neccesary with gcc. But,
could some body tell me if there are compilation problems with that? In
that case, I have to clean it.
It's unnecessary in any C compiler. Outside of preprocessor
directives, C++-style comments (//) and string or character literals,
you can use a newline anywhere that you can use a space.
--
Glynn Clements <glynn@gclements.plus.com>