From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_40,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,bac902cf9fd6564b
X-Google-Attributes: gid103376,public
From: Alfred Hilscher <Alfred.Hilscher@icn.siemens.de>
Subject: Re: Case Sensitivity
Date: 2000/05/11
Message-ID: <391AD51A.E2E64E10@icn.siemens.de>#1/1
X-Deja-AN: 622151352
Content-Transfer-Encoding: 7bit
References: <958056490.47876@hearts.q-net.net.au>
X-Accept-Language: en
Content-Type: text/plain; charset=us-ascii
Organization: Siemens AG
Mime-Version: 1.0
Newsgroups: comp.lang.ada
Date: 2000-05-11T00:00:00+00:00
List-Id: <comp.lang.ada>



Cameron McShane wrote:
> 
>     type Menu_Options is (buy, read, done)
> 
> If the user is to be allowed to enter Buy or BUY or bUy - etc, do I need to
> make the data type
> 
>     type Menu_Options is (buy, Buy, bUY, etc

Why do you think that the way a user enters input (a string ?) does
affect your internal representaion (your set type).

> or is there a way of converting user input to all lower case?

Yes, this way exists. It was mentioned in another thread a few days ago.
(Hint: conversion to upper or to lower, have a look into the manual)
 
> Any help Would be greatly appreciated.

Is this enough help ? ;-)
 
> Cheers
> Cameron

Bye.