[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Case-sensitivity of PLT web server

You are correct that your XML language may use uppercase letters in
tags, so an uppercase reader helps with this.  However, there are three
different things that could be case sensitive or not.
  a) mzscheme's default
  b) the web server
  c) each servlet

I'm not sure how to do (a).

For (b), you don't really care.  It's just a function and callers
don't need to know how I named the identifiers inside.

For (c), you can change your servlet from

(unit/sig () (import servlet^) ...)
#cs(unit/sig () (import servlet^) ...)
where the #cs stands for "case sensitive".

I just tried this and it produced case sensitive tags for me. I think
it's best that code that depends on case sensitivity (or lack there of)
specifies which it requires. Depending on the particular instance of
mzscheme's default might make it hard to combine code from different

Let me know if this resolves the issue to your satisfaction.



At Thu, 18 Apr 2002 12:56:58 +0400 (MSD), Kirill Lisovsky wrote:
> Hello! IMHO, it would be a very important improvement if PLT Web
> server will be started in case-sensitive mode "out of the box". XML
> is a case-sensitive language, and using Scheme with case-insensitive
> reader is a reason for lot of unnecessary troubles for XML/Scheme
> applications. Another example of unnecessary troubles: servlet's
> attempt to use upper-case SSAX bindings from Neil Van Dyke's package
> leads to a reference to undefined (lowercased!) identifier. For a
> while I'm looking for _simplest_ (suitable for mass deployment) way
> to switch web server in case-sensitive mode under Windows. Any ideas?
> BTW: For UNIX (where 'web-server' is a script) solution is
> straightforward: just add mzscheme's -g switch ('-qgmvL-' instead of
> '-qmvL-') in this script. Best regards, Kirill Lisovsky.