Prev: Automatically rename a downloaded file by curl to avoidfilename conflict.
Next: Man vs. standards
From: Albretch Mueller on 6 Feb 2010 07:23
> BTW, I always wonder why one writes
>
>   # input file
>   _IFl="$1"
>
> instead of
>
>   input_file="$1"
>
> Anyway.
>
> Janis
~
simply because not everybody on earth speaks English and I use the "#
input file" comment and an extra comments localization/description
file to rewrite those comments in other natutal languages
~
lbrtchx
From: Ivan Shmakov on 6 Feb 2010 09:34
>>>>> Albretch Mueller <lbrtchx(a)gmail.com> writes:

>> BTW, I always wonder why one writes

>> # input file
>> _IFl="$1"

>> instead of

>> input_file="$1"

>> Anyway.

> simply because not everybody on earth speaks English and I use the "#
> input file" comment and an extra comments localization/description
> file to rewrite those comments in other natutal languages

#ifdef ALLOW_OPINIONS

While I share the view that the i18n issues are important, I
doubt so when it comes to the representation of the source code
itself. In particular, this seems to be a sure way to prevent
whatever international collaboration the project may be worth.

Also, having obtained my English skills in large part through
the reading of programming-related texts, I could hardly imagine
a good programmer that doesn't know English to at least the
extent when no “input_file” causes a problem.

Apparently, there was a long history of the programming
languages based on natural languages other than English, which
shared much the same fate to be gone within a decade each.

#endif

--
FSF associate member #7257
From: Janis Papanagnou on 7 Feb 2010 18:41
Albretch Mueller wrote:
>> BTW, I always wonder why one writes
>>
>> # input file
>> _IFl="$1"
>>
>> instead of
>>
>> input_file="$1"
>>
>> Anyway.
>>
>> Janis
> ~
> simply because not everybody on earth speaks English and I use the "#
> input file" comment and an extra comments localization/description
> file to rewrite those comments in other natutal languages
> ~
> lbrtchx

This explanation makes no sense, given that the shell command language
constructs and the names of commands are all in English, and there are
also just a few variable names commented that way in your code. Sounds
more than a lame excuse. Not that I really care.
First  |  Prev  | 
Pages: 1 2 3
Prev: Automatically rename a downloaded file by curl to avoidfilename conflict.
Next: Man vs. standards