Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #35026

Re: Disappearing API docs

Show key headers only | View raw

On Wed, 20 Jul 2016 11:08:53 -0700, Eric Douglas wrote:

> On Wednesday, July 20, 2016 at 2:00:13 PM UTC-4, Eric Sosman wrote:
>> > Again I haven't seen any benefit of case sensitive files [...]
>> 
>>      Because a case-sensitive file system spends no CPU cycles
>> converting letters to a "canonical" case, it is more efficient.
> 
> That depends if you ever need to type your file names.  The inefficiency
> of mistyped names will likely exceed the efficiency gained from case
> insensitive matching, particularly on newer faster CPUs.
>
Actually, it goes a lot further than that because it also applies to all 
filenames in system configuration files as well as those that are hard-
coded into programs, simply because nothing can guarantee that these 
filenames are in canonical form. Simply put, every time a file is opened, 
its name must be converted to canonical form, possibly rejected as 
invalid, and if valid, compared with the filing system to see if a file 
with this name exists. This is an essential prerequisite to checking 
access permissions to see of the program is allowed to open in in the 
requested mode.
 
> Windows Explorer also has a built in search option.  Does Linux have a
> file explorer with a search?  Does it have an option for case
> insensitive?
>
Several, including 'locate' (http://linux.die.net/man/1/locate) as well 
as the search tools in graphical file managers. Locate has a case-
insensitive option, the file manager I use does not.

Then again, the shells (equivalent to the Windows command-line 
interpreter, but rather more powerful - I use the bash shell, but there 
are several others) have a filename matching ability that can be used to 
provide case sensitivity if its needed, e.g. instead of using 'myfile
[0-9].txt' to select a file with a single digit before the extension, you 
could use '[Mm]y[Ff]ile[0-9].txt' if you're unsure whether the name 
prefix is myfile or MyFile. Here's a real-life example:

$ ls [Ee]tic[Kk]et*-[1-9].pdf
Eticket-DK7203-301791-4.pdf  Eticket-GL4002-301791-1.pdf

'ls' is the UNIX/Linux 'dir' command.
  

-- 
martin@   | Martin Gregorie
gregorie. | Essex, UK
org       |

Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Disappearing API docs Roedy Green <inquiry@mindprod.com> - 2016-07-19 06:46 -0700
  Re: Disappearing API docs Eric Douglas <e.d.programmer@gmail.com> - 2016-07-19 06:54 -0700
    Re: Disappearing API docs Lew <lewbloch@gmail.com> - 2016-07-19 10:36 -0700
      Re: Disappearing API docs Roedy Green <inquiry@mindprod.com> - 2016-07-19 12:23 -0700
        Re: Disappearing API docs Eric Douglas <e.d.programmer@gmail.com> - 2016-07-19 12:49 -0700
          Re: Disappearing API docs Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-19 20:31 +0000
            Re: Disappearing API docs Eric Douglas <e.d.programmer@gmail.com> - 2016-07-19 13:59 -0700
              Re: Disappearing API docs Lew <lewbloch@gmail.com> - 2016-07-19 14:52 -0700
              Re: Disappearing API docs Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-19 22:03 +0000
                Re: Disappearing API docs Eric Douglas <e.d.programmer@gmail.com> - 2016-07-20 05:36 -0700
                Re: Disappearing API docs Nigel Wade <nmw@local.domain> - 2016-07-20 17:10 +0100
                Re: Disappearing API docs Eric Douglas <e.d.programmer@gmail.com> - 2016-07-20 10:39 -0700
                Re: Disappearing API docs Eric Sosman <esosman@comcast-dot-net.invalid> - 2016-07-20 13:59 -0400
                Re: Disappearing API docs Eric Douglas <e.d.programmer@gmail.com> - 2016-07-20 11:08 -0700
                Re: Disappearing API docs Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-20 21:55 +0000
                Re: Disappearing API docs Eric Sosman <esosman@comcast-dot-net.invalid> - 2016-07-20 18:19 -0400
                Re: Disappearing API docs Arne Vajhøj <arne@vajhoej.dk> - 2016-07-22 13:31 -0400
                Re: Disappearing API docs Nigel Wade <nmw@local.domain> - 2016-07-21 10:08 +0100
                Re: Disappearing API docs Arne Vajhøj <arne@vajhoej.dk> - 2016-07-22 13:30 -0400
                Re: Disappearing API docs Arne Vajhøj <arne@vajhoej.dk> - 2016-07-22 13:16 -0400
                Re: Disappearing API docs Gene Wirchenko <genew@telus.net> - 2016-07-22 15:24 -0700
                Re: Disappearing API docs Lew <lewbloch@gmail.com> - 2016-07-22 15:34 -0700
                Re: Disappearing API docs Arne Vajhøj <arne@vajhoej.dk> - 2016-07-22 19:29 -0400
                Re: Disappearing API docs Gene Wirchenko <genew@telus.net> - 2016-07-23 21:45 -0700
                Re: Disappearing API docs Arne Vajhøj <arne@vajhoej.dk> - 2016-07-30 22:33 -0400
                Re: Disappearing API docs Gene Wirchenko <genew@telus.net> - 2016-08-02 11:07 -0700
                Re: Disappearing API docs Eric Sosman <esosman@comcast-dot-net.invalid> - 2016-08-02 14:26 -0400
                Re: Disappearing API docs Gene Wirchenko <genew@telus.net> - 2016-08-02 15:53 -0700
                Re: Disappearing API docs Arne Vajhøj <arne@vajhoej.dk> - 2016-08-03 21:55 -0400
              Re: Disappearing API docs Arne Vajhøj <arne@vajhoej.dk> - 2016-07-19 20:43 -0400
          Re: Disappearing API docs Arne Vajhøj <arne@vajhoej.dk> - 2016-07-19 20:40 -0400
            Re: Disappearing API docs Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-20 11:45 +0000
              Re: Disappearing API docs Arne Vajhøj <arne@vajhoej.dk> - 2016-07-20 08:47 -0400
                Re: Disappearing API docs Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-20 18:44 +0000
  Re: Disappearing API docs Arne Vajhøj <arne@vajhoej.dk> - 2016-07-19 20:24 -0400

csiph-web