zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk
Subject: Re: Latest CVS + ZLE_UNICODE_SUPPORT on RHEL3
Date: Mon, 21 Feb 2005 10:56:23 +0000	[thread overview]
Message-ID: <200502211056.j1LAuOJH006163@news01.csr.com> (raw)
In-Reply-To: <1050218220111.ZM20883@candle.brasslantern.com>

Bart Schaefer wrote:
> I tried defining ZLE_UNICODE_SUPPORT and building on RHEL3 (really CentOS,
> but that shouldn't matter)

Generally speaking, I'm not that suprised, since there are large numbers
of odds and ends still to clear up (I haven't tried turning it on yet).

> and the build died on a syntax error in zle.h
> (apparently the "int_t" typedef does not exist?).

That should have been wint_t.  That's guaranteed to hold either a
wchar_t or a WEOF.

Clint and I have added various type and functions like this without there
being any tests in configure: this is one reason we're currently relying
on the compiler offering support.  If we want to relax that assumption
later, we'll probably have to work out what to do if wchar_t is defined
and wint_t isn't, etc.  I suppose the answer in this case is probably
just stick with wchar_t.  But that's all Zukunftsmusik.


Index: Src/Zle/zle.h
===================================================================
RCS file: /cvsroot/zsh/zsh/Src/Zle/zle.h,v
retrieving revision 1.7
diff -u -r1.7 zle.h
--- Src/Zle/zle.h	18 Feb 2005 13:57:28 -0000	1.7
+++ Src/Zle/zle.h	21 Feb 2005 10:49:02 -0000
@@ -30,7 +30,7 @@
 #ifdef ZLE_UNICODE_SUPPORT
 typedef wchar_t ZLE_CHAR_T;
 typedef wchar_t *ZLE_STRING_T;
-typedef int_t   ZLE_INT_T;
+typedef wint_t   ZLE_INT_T;
 #define ZLE_CHAR_SIZE	sizeof(wchar_t)
 
 /*

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

**********************************************************************


  reply	other threads:[~2005-02-21 10:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-18 22:01 Bart Schaefer
2005-02-21 10:56 ` Peter Stephenson [this message]
     [not found] <E1D3Ddp-000JDB-00.arvidjaar-mail-ru@f30.mail.ru>
2005-02-21 13:37 ` Borzenkov Andrey
2005-02-21 14:29   ` Peter Stephenson
2005-02-21 19:13     ` Andrey Borzenkov
2005-02-22 10:12       ` Peter Stephenson
2005-02-22 10:48         ` Peter Stephenson
2005-02-22 13:36           ` Oliver Kiddle

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=200502211056.j1LAuOJH006163@news01.csr.com \
    --to=pws@csr.com \
    --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).