From: Jeff Mullen <cpu.write@verizon.net>
To: xconq7@sources.redhat.com
Subject: Newbie Looking for Some Answeres
Date: Sat, 17 May 2008 22:55:00 -0000 [thread overview]
Message-ID: <482F6238.40101@verizon.net> (raw)
I'm basically exploring Xconq, and went to check out the "Advances
Through History" set-up. It's left me scratching my head.
I can't get 20 turns into the scenario without the program just up and
terminating. It always happens after I try to put in a new research
goal. I'm running under freespire 1.0 on an IBM PC compatible that I
built myself. I'm a long time C Programmer.
This is a bug of one kind or another.
If I'm losing the game and it's not telling me this, it's a design bug.
If it's running into some contradiction in the research goals that it
simply can't handle and giving up without so much as printing an Fatal
Error Message, then it's a coding bug. Even if my machine is running
out of memory (one of the $#@)(! RAM sticks went bad and I haven't had a
chance to replace it yet, so I'm down to a measly 256 megs of the ol'
PC2100), there should be some indication that this is what is
happening. There isn't. The program just stops running.
Either way, I'm being left high and dry, and it's really annoying me.
Whenever one designs a program, one should have it provide something
called "graceful degradation"--that is, when it bombs, IT SHOULD GIVE
YOU SOME IDEA AS TO WHY!!!!!!!!!!!!!
Any help would be appreciated. Please reply to the email address from
which this message was sent, as I have no idea what the mailing list is
let alone how to get on it, and I'm not in any mood right now to spend
the time to find out.
Any help that could be given will be appreciated. I promise that I'll
be calmed down and nice and shiny polite by the time I reply to any
replies. No need to mistreat folks who are trying to help. Thanks in
advance.
Jeff
next reply other threads:[~2008-05-17 22:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 22:55 Jeff Mullen [this message]
2008-05-18 22:47 ` Lincoln Peters
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=482F6238.40101@verizon.net \
--to=cpu.write@verizon.net \
--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).