|
![](/i/fill.gif) |
On 16-5-2016 23:25, Alain wrote:
>> Alain <kua### [at] videotron ca> wrote:
>>
>>>
>>> If you are under Windows, file paths, including files names, are always
>>> case insencitive.
>>>
>>
>> Really?! That is something I didn't know. In all my years of using
>> POV-Ray on
>> Windows, I've always been extremely careful to spell file names
>> exactly as they
>> should be-- when I didn't have to be so precise, apparently! Strange
>> that I've
>> never noticed that before.
>>
>> Thanks!
>>
>> Actually, I think that it's going to be hard for me to get used to
>> this 'new'
>> idea (new to me!)-- trying to change about 15 years' worth of old
>> habits. Ha!
>>
>>
>
> It's a leftover from DOS 1.0. DOS 0.1 alpha to DOS 7.xx, and Windows 1.0
> to Windows 10, have always been case insencitive. But, who know, maybe
> in some future time Windows could become case sencitive...
> Also, the infamous backslash "\" comes from the bad decision of using
> the forward slash for switches and command lines options that where not
> to be set ON/Off (+ -) but activated by presence, like dir /w. They also
> used the pipe "|" in some cases for no real reasons.
>
Like Kenneth, I have never been aware of that either! It won't change my
habit though ;-)
The use of "|" in e.g. #if (x>10 | z<=20) is legitimate though? What
other, invalid, use are you talking of?
--
Thomas
Post a reply to this message
|
![](/i/fill.gif) |