| Re: [AD] Re: file_select_ex patch |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] Re: file_select_ex patch
- From: Chris <chris.kcat@xxxxxxxxxx>
- Date: Fri, 16 Sep 2005 16:29:05 -0700
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=LD635LaSttBG+hSBWWBpYnayp/sQlVleU5W7i5I74cff2x+kvSHjXO5Q2nfz/DxRYQI89hZR0SsRUF9nOvNO99qo1qCb1fbSFD7XxtORcT3cvnFGL86MC7jTIguBHJqN771KSrPLttTvAi5AUByopGG5JeBZ8OdzfyB5CZk3FHM=
On Friday 16 September 2005 04:17 pm, Michal Molhanec wrote:
> what do you mean by smart? the app simply writes the files into cwd, it
> is not interested in any filesystem flags
Then it's a bad program. It should be very cautious of the filesystem flags.
> > In all actuality, it shouldn't be able to create those
> > files in a read-only directory without first clearing the read-only
> > attribute.
>
> but it is able to do that
Through a short-coming of Windows's filesystem. Do the same thing in
Linux/OSX/Unix, and I guarantee it'll fail horribly.
> > But the directory is marked read-only. You *shouldn't* be able to create
> > new files there, or delete existing ones.
>
> but you *are* able to do that
Just because Windows allows it doesn't mean it's proper behavior.