From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Elijah Meeks <elijahmeeks@yahoo.com>
Cc: xconq7@sources.redhat.com
Subject: Re: Table Request: Accident-Occupant-Effect
Date: Thu, 23 Sep 2004 18:23:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0409231350450.10556-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <20040923150900.81622.qmail@web13121.mail.yahoo.com>
On Thu, 23 Sep 2004, Elijah Meeks wrote:
> (unit college-student (auto-upgrade-to dropout)
> (auto-upgrade-to wageslave) (auto-upgrade-to
> engineer))
The way Xconq parses things is such that the final value of the
'auto-upgrade-to' property would be 'engineer', as the other
previously assigned values would be clobbered.
I did consider making 'auto-upgrade-to' a table rather than an
unit property when I was first implementing that stuff. But, I
opted for a property so that there would be no ambiguities. If it
was a table, then there would be the possibility of multiple
auto-upgrade paths, and if certain material and size conditions
were fulfilled simultaneously, then how would the code be able to
tell which upgrade path to take? Since the auto-upgrade code is
kernel-level, it cannot (should not) make subjective decisions,
and so I thought it better to restrict auto-upgrade paths to be
completely predetermined.
> Though the example's meant to be funny (dropout is
> probably a wreck-type),
:-)
> Sure, sounds great, but before you leave...
Uh oh. At least your message didn't end in "and, and, and...".
Eric
prev parent reply other threads:[~2004-09-23 17:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 1:40 Elijah Meeks
2004-09-23 2:26 ` mskala
2004-09-23 5:38 ` Eric McDonald
2004-09-23 15:09 ` Elijah Meeks
2004-09-23 17:59 ` Eric McDonald
2004-09-24 1:51 ` Elijah Meeks
2004-09-23 3:10 ` Eric McDonald
2004-09-23 17:47 ` Elijah Meeks
2004-09-23 18:23 ` Eric McDonald [this message]
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.44.0409231350450.10556-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=elijahmeeks@yahoo.com \
--cc=xconq7@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).