From: Luke A. Guest <laguest@archeia.com>
Subject: Re: no code generation for c strings
Date: Fri, 3 Jun 2016 22:33:11 +0100
Date: 2016-06-03T22:33:11+01:00 [thread overview]
Message-ID: <1763916289.486682087.099848.laguest-archeia.com@nntp.aioe.org> (raw)
In-Reply-To: ly1t4eq81y.fsf@pushface.org
Simon Wright <simon@pushface.org> wrote:
> Luke A. Guest <laguest@archeia.com> writes:
>> I'm still not sure why your way of doing this produced the desired effect
>> though.
>
> Possibly because it was in a spec? Yours was in a library-level
> subprogram, so there would have been no need for a related symbol?
>
No, I mean I don't understand why this:
S : constant char_array := "hello" & char'val(0);
Produces the statically allocated string without using the secondary stack.
I know that using to_c will utilise it. Unsurprised the compiler doesn't
think that string is of type string. I tried something similar without the
end from the ampersand onwards and it complained of different types.
prev parent reply other threads:[~2016-06-03 21:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 8:14 no code generation for c strings Luke A. Guest
2016-06-03 8:25 ` Dmitry A. Kazakov
2016-06-03 9:23 ` Luke A. Guest
2016-06-03 9:37 ` Dmitry A. Kazakov
2016-06-03 14:27 ` G.B.
2016-06-03 17:00 ` Lucretia
2016-06-04 6:31 ` Georg Bauhaus
2016-06-03 16:30 ` Simon Wright
2016-06-03 17:04 ` Lucretia
2016-06-03 18:45 ` Simon Wright
2016-06-03 20:30 ` Luke A. Guest
2016-06-03 21:25 ` Simon Wright
2016-06-03 21:33 ` Luke A. Guest [this message]
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox