zsh-workers
 help / color / mirror / code / Atom feed
From: Paul Ackersviller <pda@sdf.lonestar.org>
To: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Compilation error in Src/Modules/curses.c on HP-UX
Date: Mon, 17 Dec 2007 00:41:33 +0000	[thread overview]
Message-ID: <20071217004133.GB11772@sverige> (raw)
In-Reply-To: <20071216193143.ac75ef46.p.w.stephenson@ntlworld.com>

I've apparently been using ncurses with this until now, but I just
happened to try out HP's curses library instead, and encounter this error. 

cc: "curses.c", line 1332: error 1000: Unexpected symbol: "{".
cc: "curses.c", line 1332: error 1000: Unexpected symbol: "==".
cc: "curses.c", line 1333: error 1000: Unexpected symbol: "{".
cc: "curses.c", line 1333: error 1588: "__wi" undefined.

It only happens with the HP compiler, gcc seems to cope with the code
even though the curses.h it uses is very similar.  Given that the macro
looks like

#define getyx(__win,__y,__x)    { WINDOW *__wi; \
                 __wi = __win; ((__y) = __getcury(__wi), \
                 (__x) = __getcurx(__wi)); }

I'm not quite sure what is meant or what gcc is giving us out of
the macro call:

1331     /* Look no pointers:  these are macros. */
1332     if (getyx(w->win, intarr[0], intarr[1]) == ERR ||
1333   getbegyx(w->win, intarr[2], intarr[3]) == ERR ||
1334   getmaxyx(w->win, intarr[4], intarr[5]) == ERR)
1335   return 1;


  parent reply	other threads:[~2007-12-17  0:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-16 14:08 Release status update Peter Stephenson
2007-12-16 17:37 ` Mutt mailbox completion with "=" (was: Release status update) Vincent Lefevre
2007-12-16 19:31   ` Peter Stephenson
2007-12-16 21:46     ` Vincent Lefevre
2007-12-17  0:41     ` Paul Ackersviller [this message]
2007-12-17  1:42       ` Compilation error in Src/Modules/curses.c on HP-UX Wayne Davison
2007-12-18 16:22         ` Paul Ackersviller

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=20071217004133.GB11772@sverige \
    --to=pda@sdf.lonestar.org \
    --cc=zsh-workers@sunsite.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).