From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: random thoughts on DEPRECATED and OBSOLETE
Date: Sat, 28 Apr 2007 19:38:33 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0704281933160.29552@localhost.localdomain> (raw)
In-Reply-To: <4633CA7F.6010505@s5r6.in-berlin.de>
On Sun, 29 Apr 2007, Stefan Richter wrote:
> I see a discussion on OBSOLETE vs. BROKEN there, which even ended in
> a consensus, but I do not see an explicit discussion on OBSOLETE vs.
> DEPRECATED.
i think this online definition matches what i have in mind:
http://www.google.com/search?hl=en&rls=GGGL,GGGL:2006-10,GGGL:en&defl=en&q=define:Deprecated&sa=X&oi=glossary_definition&ct=title
"A deprecated element or attribute is one that has been outdated by
newer constructs. Deprecated elements are defined in the reference
manual in appropriate locations, but are clearly marked as deprecated.
Deprecated elements may become obsolete in future versions of HTML. We
recommend that authors avoid using deprecated elements and attributes
whenever practical."
note carefully how deprecated elements can still be used, but their
use is discouraged and they *may become obsolete*. that's exactly
what i was getting at. deprecated stuff *might* still be used;
obsolete stuff *shouldn't* be used.
rday
p.s. just FYI, even *i'm* getting bored of this. :-)
next prev parent reply other threads:[~2007-04-28 23:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 13:25 Robert P. J. Day
2007-04-28 16:52 ` Stefan Richter
2007-04-28 18:05 ` Robert P. J. Day
2007-04-28 20:21 ` Stefan Richter
2007-04-28 20:26 ` Stefan Richter
2007-04-28 21:04 ` Robert P. J. Day
2007-04-28 22:28 ` Stefan Richter
2007-04-28 23:31 ` Robert P. J. Day
2007-04-29 0:29 ` Stefan Richter
2007-04-28 23:38 ` Robert P. J. Day [this message]
2007-04-29 0:22 ` Stefan Richter
2007-04-29 6:34 ` Robert P. J. Day
2007-04-28 23:21 ` Tilman Schmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0704281933160.29552@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®