TC wrote:
> Well, if it is open source, why don't you fix it?

I have, in other situations. It's difficult to get involved enough to fix 
all of them. And in part for the same reasons the original authors didnt: 
it's not enough of a pain to me to do that. But it's much more of a pain for 
me to fix it than it is for the original authors to do it right in the first 
place. :-)

-- 
Darren New, San Diego CA, USA (PST)
   Human nature dictates that toothpaste tubes spend
   much longer being almost empty than almost full.

Post a reply to this message

Darren New <dne### [at] sanrrcom> wrote:
> Warp wrote:
> > Darren New <dne### [at] sanrrcom> wrote:
> >> Warp wrote:
> >>> Darren New <dne### [at] sanrrcom> wrote:
> >>>> Somehow, I always find it amusing how many FOSS programs assume Windows is 
> >>>> basically how it was in Win98 and completely fail to do the right thing.
> >>>   Well, you can always demand your money back.
> > 
> >> Sometimes you're extremely predictable.
> > 
> >   Well, if the argument is valid, why change it?

> You're predictable in that you make that argument even when nobody else is 
> arguing. :-)

  I don't think that presenting an argument is the same thing as "arguing"
(ie. to contend in oral disagreement).

-- 
                                                          - Warp

Post a reply to this message

Warp wrote:
> Darren New <dne### [at] sanrrcom> wrote:
>> Warp wrote:
>>> Darren New <dne### [at] sanrrcom> wrote:
>>>> Warp wrote:
>>>>> Darren New <dne### [at] sanrrcom> wrote:
>>>>>> Somehow, I always find it amusing how many FOSS programs assume Windows is 
>>>>>> basically how it was in Win98 and completely fail to do the right thing.
>>>>>   Well, you can always demand your money back.
>>>> Sometimes you're extremely predictable.
>>>   Well, if the argument is valid, why change it?
> 
>> You're predictable in that you make that argument even when nobody else is 
>> arguing. :-)
> 
>   I don't think that presenting an argument is the same thing as "arguing"
> (ie. to contend in oral disagreement).

You're very predictable in that you present that argument every time someone 
says something about FOSS.

In any case, wouldn't you think it rather lame if (for example) Mono only 
read text files that had lines terminated in CRLF? Or if you frequently ran 
across large complex Linux programs that assumed "~fred/x" should expand to 
"/home/fred/x" regardless of what was in /etc/passwd?

They should at least stop putting misinformation in the documentation like 
"you can't delete open files in Windows" or "Windows doesn't have links". 
That's just plain wrong. The minimum would be to phrase it as "we don't open 
files in a mode that allows them to be deleted while open" and "we don't 
support links in Windows".

-- 
Darren New, San Diego CA, USA (PST)
   Human nature dictates that toothpaste tubes spend
   much longer being almost empty than almost full.

Post a reply to this message

Darren New <dne### [at] sanrrcom> wrote:
> They should at least stop putting misinformation in the documentation like 
> "you can't delete open files in Windows" or "Windows doesn't have links". 
> That's just plain wrong. The minimum would be to phrase it as "we don't open 
> files in a mode that allows them to be deleted while open" and "we don't 
> support links in Windows".

  It's an open source project. You can contribute.

-- 
                                                          - Warp

Post a reply to this message

Warp wrote:
> Darren New <dne### [at] sanrrcom> wrote:
>> They should at least stop putting misinformation in the documentation like 
>> "you can't delete open files in Windows" or "Windows doesn't have links". 
>> That's just plain wrong. The minimum would be to phrase it as "we don't open 
>> files in a mode that allows them to be deleted while open" and "we don't 
>> support links in Windows".
> 
>   It's an open source project. You can contribute.

Wow, really?? Thanks, Warp! I didn't know that!

-- 
Darren New, San Diego CA, USA (PST)
   Human nature dictates that toothpaste tubes spend
   much longer being almost empty than almost full.

Post a reply to this message

> They should at least stop putting misinformation in the documentation like 
> "you can't delete open files in Windows" or "Windows doesn't have links". 
> That's just plain wrong. The minimum would be to phrase it as "we don't 
> open files in a mode that allows them to be deleted while open" and "we 
> don't

Darren, how do you delete an OS-locked file or directory under Windows XP? 
Can you point me to an api-call?

This is NOT meant as a tease, I am really interested in a solution to this 
problem, if you know it.

About the links: yes, windows does indeed support links. I do not dare to 
use them anymore. I tried once, but since people don't expect hard links 
under Windows to some it came as a nasty surprise when they discovered the 
doublettes they thought they were deleting were the actually hard linked 
files...

Post a reply to this message

Darren New wrote:
> Warp wrote:
>> Darren New <dne### [at] sanrrcom> wrote:
>>> They should at least stop putting misinformation in the documentation 
>>> like "you can't delete open files in Windows" or "Windows doesn't 
>>> have links". That's just plain wrong. The minimum would be to phrase 
>>> it as "we don't open files in a mode that allows them to be deleted 
>>> while open" and "we don't support links in Windows".
>>
>>   It's an open source project. You can contribute.
> 
> Wow, really?? Thanks, Warp! I didn't know that!

Wait, wait!  I have an even better idea!

I can go around the internet and correct *everyone* who says something 
wrong! I'm sure that will improve the world and make me loved and respected 
everywhere!

-- 
Darren New, San Diego CA, USA (PST)
   Human nature dictates that toothpaste tubes spend
   much longer being almost empty than almost full.

Post a reply to this message

TC wrote:
> Darren, how do you delete an OS-locked file or directory under Windows XP? 

You don't lock it.  It's not that you can't delete an *open* file. You can't 
delete an open file that was opened with the "don't let others write to this 
while I have it open" flag.  The program opening the file has to open it in 
a way that lets you delete it, which is why I'm saying I'm surprised that 
(for example) the usual C runtimes don't default to setting this flag, since 
that's the default under UNIX.

The primary problem is that the call to run a program opens the file with 
that lock, in part because it pages out of the file while it's running. The 
file gets locked because to delete a file in Windows you actually have to 
open the file for delete, which requires write privileges. Opening an 
executing file for writing doesn't work under Windows *or* UNIX, but you 
don't have to open the file under UNIX to delete it.

Alternately, you can stick stuff in the registry that'll delete the file (or 
rename it) next time the machine is booted, before all the code that tends 
to hold files open runs, if that's what you mean.

> Can you point me to an api-call?

It's just a normal delete.

> About the links: yes, windows does indeed support links. I do not dare to 
> use them anymore. I tried once, but since people don't expect hard links 
> under Windows to some it came as a nasty surprise when they discovered the 
> doublettes they thought they were deleting were the actually hard linked 
> files... 

Well, yes. That's not a good reason for a programming environment not to use 
them. It's just a good reason to be careful how you expose that to your 
users. :-)

-- 
Darren New, San Diego CA, USA (PST)
   Human nature dictates that toothpaste tubes spend
   much longer being almost empty than almost full.

Post a reply to this message

Darren New wrote:
> Somehow, I always find it amusing how many FOSS programs assume Windows 
> is basically how it was in Win98 and completely fail to do the right thing.

...which does, on the other hand, have the side-effect of making it 
compatible with Win98. ;-)

> which in other words means "we haven't bothered to find the API call 
> that tells you where a particular user's home directory is in Windows, 

Or, more likely, "we just took our C sources and recompiled them on top 
of a POSIX emulator, so we can't do anything that POSIX doesn't support 
/ the emulator doesn't implement".

> And some people wonder why FOSS feels klunky on Windows.

Heh, well, the *really* fun thing is when you have to install GTK+ 
before the program will run... We all know what happens then. ;-)

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message

Darren New <dne### [at] sanrrcom> wrote:
> Warp wrote:
> > Darren New <dne### [at] sanrrcom> wrote:
> >> They should at least stop putting misinformation in the documentation like 
> >> "you can't delete open files in Windows" or "Windows doesn't have links". 
> >> That's just plain wrong. The minimum would be to phrase it as "we don't open 
> >> files in a mode that allows them to be deleted while open" and "we don't 
> >> support links in Windows".
> > 
> >   It's an open source project. You can contribute.

> Wow, really?? Thanks, Warp! I didn't know that!

  And then you criticize me when I use sarcasm.

-- 
                                                          - Warp

Post a reply to this message