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


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

Re: Disappearing API docs

Newsgroups comp.lang.java.programmer
Date 2016-07-20 10:39 -0700
References (5 earlier) <nmm2nv$ohp$1@dont-email.me> <27115dc3-85aa-4305-99bd-fdfdb28f390a@googlegroups.com> <nmm842$e7q$2@dont-email.me> <859110c7-ef6c-421d-8d26-69020e21d094@googlegroups.com> <dv9m4gFi9rgU6@mid.individual.net>
Message-ID <f0cf6d8e-91cc-4245-9703-291c8448e652@googlegroups.com> (permalink)
Subject Re: Disappearing API docs
From Eric Douglas <e.d.programmer@gmail.com>

Show all headers | View raw


On Wednesday, July 20, 2016 at 12:11:08 PM UTC-4, Nigel Wade wrote:
> Have you never noticed that Javadoc is case sensitive?
duh
> How else would it correctly differentiate the case of classes/methods/members?
> 
> Try using a Javadoc classname URL which has incorrect case, e.g.
> https://docs.oracle.com/javase/8/docs/api/java/util/Arrays.html
> https://docs.oracle.com/javase/8/docs/api/java/util/arrays.html

Ever hear of a method called compareToIgnoreCase()?

> > Unless you want to obscure your publicly available data making it hard for anyone to get to without a link it doesn't make sense.
> 
> Why would using case sensitivity make your data hard to find?
> How often do you actually type in a URL (as opposed to just a website address)?

So you just assume no one will ever type in a url, and it's case will never change otherwise all existing links will be broken.  Of course the domain can't be case sensitive or phishers would be signing up for Yahoo.com, YAHOO.COM, etc.  Why would you need the rest of it to be case sensitive?  Do you have any examples of a url that gets 2 valid pages with different case?  Can you get 2 of the same email address with different case?  If they can find any domain case insensitive why should it be so hard to find a page on that domain with different case.

> >
> > Either it's rare for anyone to host a web site on a case sensitive OS, or case sensitive OS normally use a flag that changes all urls to lower case?
> 
> I suspect the majority of the WWW is hosted on case-sensitive systems.
> The typical LAMP stack has case-sensitive filesystems, and Apache is case-sensitive by default.

Majority?  Where do you get that statistic?  I tried changing case on NPR and it found the page.  I tried the same on ABC News and it found the page.  Case insensitive would seem the norm at least for news sites.  I would think most people would prefer case insensitive especially where there are shorter URLs their customers might be more likely to type in and get wrong.

> Since you haven't noticed, it's probably safe to assume it's not a problem.

I expect most of the time it isn't.  My company pays someone else to host our web site and they put it on Apache so we have the same problem with case sensitive.  This could be causing problems we don't even know about, if a potential customer typed in the url and couldn't find a page and gave up, but no one has mentioned any.  Just because it's not an apparent problem doesn't mean it's a good idea.

> >
> > I don't even know the point of a case sensitive OS as I've only seen it create problems.
> 
> A case sensitive fileystem is as important as a case sensitive language (both natural and computer). Case conveys information.
> It doesn't cause any problems unless it's paired with a system which is not case-sensitive, or a user who doesn't understand it.

Again I haven't seen any benefit of case sensitive files but I have seen it create problems.  What information are you trying to convey exactly with case in a filename, and what does that have to do with finding a web page without matching case?

> > If you have a unix server and a Windows client and you want to update program1 you have to make sure your file is not called PROGRAM1 and you can't rename PROGRAM1 to program1 on Windows without naming it something else first...
> >
> 
> If you setup Samba correctly then you can rename the files. You can have multiple files with what to Windows would be the same name,
> e.g. test.txt, Test.txt TEST.TXT are all possible simultaneously, visible to Windows and editable by Windows. You can also rename them.
> Any problem is entirely the fault of Windows and its lack of proper support for case sensitive file names.
> Linux does it properly. Samba attempts to do what it can but is constrained by Windows limitations.

Oh a Linux fanboy trying to put down Windows for never supporting a feature most everyone can live without.  I haven't seen Samba.  As I recall we just copied files from Windows to Unix with a basic ftp command.

> I don't program on Windows so I don't know how javac on Windows manages Java classes which are not in files with the correct case filenames.
> For example, suppose for some perverse reason you wanted the classes AbcDef and Abcdef. How would Java on Windows cope with the source and class files?

Without testing I would guess it gets an error because I don't type commands to compile Java and Eclipse doesn't accept it.  If I create a class file Test.java in Eclipse and put a declaration public class TEST { I get an error "The public type TEST must be defined in it's own file".  If I create a class file Test and select the New Java Class option and put in TEST I get an error "Type with same name but different case exists".  Where have you ever seen, or why would you ever want, 2 classes in the same package with the same name different case?

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