Re: Buffer contents well-defined after fgets() reaches EOF ?

On 10.02.2025 07:41, Keith Thompson wrote:

Janis Papanagnou <janis_papanagnou+ng@hotmail.com> writes:

On 10.02.2025 05:37, Keith Thompson wrote:

[...]

This is already off-topic, so I won't even mention tabs vs. spaces.

>
But as Vim users we don't have any issues here; as long as the
indentation is _visibly_ consistent we can fix any tab/space-mix
on the fly and easily with Vim.

 
Yes, *if* the indentation is visibly consistent.
 
At a previous job, I reviewed an update whose apparent meaning
differed depending on whether the editor was configured with 4- or
8-column tabstops.  I don't remember the exact details, but the code
looked like either:
 
    if (condition)
        statement1;
    statement2;
 
or:
 
    if (condition)
        statement1;
        statement2;
 
depending on the reader's settings.  Of course they're semantically
equivalent, but the first is the way the developer saw it, and the
second is misleading and is the way it looked to me.

Yeah, misleading code is a pain, especially if you have got the job
to fix some error in these incoherent formatted modules. (I suppose
that case is yet more than only misleading if you are programming in
Python where indentation even carries semantics.)

 
This kind of thing is why I use only spaces for indentation

I think it's personal preference. Mine is to use only tabs (with a
data type specific width) for the indentation.

Janis

and curly
braces even when there's only one statement in the block (unless I'm
working under a coding standard that says otherwise).