Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 27 May 2003 10:12:14 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: is getpass function in cygwin obsolete? Message-ID: <20030527081214.GD19957@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <000901c32425$d24fc960$200aa8c0 AT thorin> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000901c32425$d24fc960$200aa8c0@thorin> User-Agent: Mutt/1.4.1i On Tue, May 27, 2003 at 03:58:33PM +0800, Carlo Florendo wrote: > [getpass] > > "This function is obsolete. Do not use it." > > http://www.opengroup.org/onlinepubs/007908799/xsh/unistd.h.html > and it labels the function as "legacy". > > I've googled the definition of legacy functions using the keywords: > 1. "legacy functions" > 2. C, "legacy code" > [...] > but I could only guess what legacy code means. (obsolete?, deprecated?, not supported anymore?) "Legacy" are functions which are defined in some early OSes (say, System 7) and which have turned out to be not exactly useful or their definition is dumb or something. They are obsolete, deprecated and not really supported anymore ;-) They won't live any longer than absolutely necessary and we will stop supporting it really soon now, probably in 2045 or so. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/