From: Brantley Coile <brantley@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] const
Date: Wed, 7 Dec 2005 14:36:58 -0500 [thread overview]
Message-ID: <38030ccb65b546888f61a63eb42b6656@coraid.com> (raw)
In-Reply-To: <7871fcf50512071130m475c7240i3c65da1b4c900c15@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 285 bytes --]
It was a way to move the string from the data segment to the text segment.
I never found it useful and making strings const char * broke lots
of programs that wrote directly into strings. No big deal, but a useless pain.
I tire of paying for things I don't use. :(
1011 1100
[-- Attachment #2: Type: message/rfc822, Size: 3493 bytes --]
From: Joel Salomon <joelcsalomon@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] const
Date: Wed, 7 Dec 2005 14:30:17 -0500
Message-ID: <7871fcf50512071130m475c7240i3c65da1b4c900c15@mail.gmail.com>
On 12/7/05, Charles Forsyth <forsyth@terzarima.net> wrote:
> (on unix) cc -S something.c
> ./:rofix something.s
> as -o something.o something.s
>
> where :rofix is a sh/ed/sed script that changes certain .data to .text
So it does the optimization possible with const. Not the "interface"
part, though. If you don't like type decorations, I guess this way's
better.
--Joel
next prev parent reply other threads:[~2005-12-07 19:36 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 10:34 Steve Simon
2005-12-07 12:17 ` Russ Cox
2005-12-07 13:01 ` erik quanstrom
[not found] ` <000401c5fb32$64502e00$14aaa8c0@utelsystems.local>
2005-12-07 14:10 ` "Nils O. Selåsdal"
2005-12-07 15:05 ` Steve Simon
2005-12-07 15:30 ` Lucio De Re
2005-12-07 15:53 ` C H Forsyth
[not found] ` <1E68F99F-78D7-4321-BE56-7D0319212596@telus.net>
2005-12-07 16:11 ` "Nils O. Selåsdal"
2005-12-07 17:27 ` Paul Lalonde
2005-12-07 16:23 ` jmk
2005-12-07 17:28 ` Skip Tavakkolian
2005-12-07 18:51 ` Joel Salomon
2005-12-07 18:58 ` Charles Forsyth
2005-12-07 19:30 ` Joel Salomon
2005-12-07 19:36 ` Brantley Coile [this message]
2005-12-07 19:51 ` rog
2005-12-07 21:07 ` Charles Forsyth
2005-12-07 21:18 ` Bruce Ellis
2005-12-07 21:22 ` Paul Lalonde
2005-12-07 22:04 ` Rob Pike
2005-12-07 22:44 ` Micah Stetson
2005-12-07 22:44 ` Micah Stetson
2005-12-07 22:46 ` Brantley Coile
2005-12-07 20:33 ` Skip Tavakkolian
2005-12-08 7:39 ` geoff
2005-12-08 7:53 ` Lucio De Re
2005-12-08 7:54 ` geoff
2005-12-08 10:23 ` Bruce Ellis
2005-12-08 15:58 ` Brantley Coile
2005-12-09 1:44 ` geoff
2005-12-09 2:04 ` Russ Cox
2005-12-09 2:19 ` geoff
2005-12-09 9:54 ` Charles Forsyth
2005-12-09 16:25 ` David Leimbach
2005-12-09 16:59 ` Richard Bilson
2005-12-09 17:42 ` David Leimbach
2005-12-09 19:17 ` Richard Bilson
2005-12-09 17:01 ` Ronald G Minnich
2005-12-09 17:39 ` Russ Cox
2005-12-09 17:40 ` [9fans] PCICIA Modem TamTam
2005-12-09 18:59 ` Sascha Retzki
2005-12-12 15:07 ` Paweł Lasek
2005-12-26 9:00 ` Martin C. Atkins
2005-12-26 14:19 ` Paweł Lasek
2005-12-09 19:37 ` [9fans] Re: const Nikita Danilov
2005-12-09 20:30 ` Russ Cox
2005-12-09 20:37 ` Ronald G Minnich
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=38030ccb65b546888f61a63eb42b6656@coraid.com \
--to=brantley@coraid.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).