From: Hans Ronne <hronne@comhem.se>
To: xconq7@sources.redhat.com
Subject: Note to game designers
Date: Sat, 17 Jul 2004 03:54:00 -0000 [thread overview]
Message-ID: <l03130300bd1dc27658ce@[212.181.162.155]> (raw)
There used to be a problem with random crashes due to buffer overflow in
the game blurb. I have now fixed that, and also increased the size of the
blurb. It can now hold up to 480 characters, and anything beyond that is
just truncated instead of crashing the game. Furthermore, the blurb is now
a lisp object instead of a string, so you don't have to write it all on a
single line in the game file. Instead, enclose multpile strings within a
parenthesis, if necessary:
(blurb (
"first string"
"second string"
"third string"
))
and they are concatenated just like the notices and instructions strings.
An empty string "" inserts a linefeed.
I have also tweaked the interfaces so that the blurb gets more space.
The idea is not to have gigantic blurbs in the future- you should still try
to keep it short and concise- but a little more room doesn't hurt.
Hans
reply other threads:[~2004-07-16 18:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='l03130300bd1dc27658ce@[212.181.162.155]' \
--to=hronne@comhem.se \
--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).