Aren/NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Be the wiz. Update the date. New sentence, new line. Slightly

Browse Source 
clarify the circumstances under which the compiler/linker will
merge strings (identical & read-only; how could it do otherwise?)

This, and the other stuff Christos has done is partly an answer
to PR 25835.
This commit is contained in:
fair 2004-06-06 08:19:56 +00:00
parent 836ba5076b
commit 6517f6d315
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
usr.bin/xstr/xstr.1
View File

@ -1,4 +1,4 @@
.\" $NetBSD: xstr.1,v 1.13 2004/06/06 07:09:02 christos Exp $
.\" $NetBSD: xstr.1,v 1.14 2004/06/06 08:19:56 fair Exp $
.\"
.\" Copyright (c) 1980, 1993
.\" The Regents of the University of California. All rights reserved.
@ -29,7 +29,7 @@
.\"
.\" @(#)xstr.1 8.2 (Berkeley) 12/30/93
.\"
.Dd December 30, 1993
.Dd June 6, 2004
.Dt XSTR 1
.Os
.Sh NAME
@ -176,8 +176,8 @@ the string, or use the following ugly hack.
.Pp
Also,
.Nm
cannot initialize structures and unions that contain strings. Those can
be fixed by changing from:
cannot initialize structures and unions that contain strings.
Those can be fixed by changing from:
.Bd -literal
struct foo {
int i;
@ -209,4 +209,5 @@ and the linker to merge strings appropriately.
Finally,
.Nm
is not very useful these days because most of the string merging is done
automatically by the compiler and the linker.
automatically by the compiler and the linker, provided that the strings
are identical and read-only.