From: Ethan Gardener <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: "constructor must be a structure" for Rune?
Date: Fri, 14 Dec 2018 13:37:00 +0000 [thread overview]
Message-ID: <1544794620.3485483.1609148640.35DFD112@webmail.messagingengine.com> (raw)
I want to put a literal rune string into a program to test a new function, but get this error:
6c -FTVw test.c
test.c:65 constructor must be a structure
mk: 6c -FTVw test.c : exit status=rc 1676: 6c 1678: error
test.c lines 64 & 65:
dcrunestring(fg, Pt(50,350),
(Rune){0x2308, 0x2190, 0x2395, 0x2192, 0x230a});
in /amd64/include/u.h:
typedef uint Rune;
What am I doing wrong? Am I doing anything wrong? Is there a way to pass a literal array like that when a pointer to an array is called for? I know I can do it by assigning to a variable first, perhaps I should just do that. It's normally my policy to use temporary variables when lines get long, but strong typing makes it a bit more of a fuss.
reply other threads:[~2018-12-14 13:37 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=1544794620.3485483.1609148640.35DFD112@webmail.messagingengine.com \
--to=eekee57@fastmail.fm \
--cc=9front@9front.org \
/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).