Problem with xstr

[Hitoshi Aida]

In article <145 at taux02.UUCP> amos at taux02.UUCP (Amos Shapir) writes:
>Unless you use a pdp11 with separate  I/D space, the solution is to just
>throw out all  the xstr stuff from your makefiles,  and compile normally
>instead.
>Xstr is a hack for putting  strings, which are supposed to be read-only,
>into the executable's  text (code) space. This makes more  room for data
>on  machines  with  limited  address space.  On  32-bit  machines,  this
>approach is obsolete and causes more trouble than benefit.

No!  You can't put strings into code segment on separate I/D machines!
The reason why xstr makes more room is because same strings will be shared
within a program, not because they will go to code segment.
--------
Hitoshi AIDA (aida at csl.sri.com)
Computer Science Lab, SRI International