All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Stefaniuc <mstefani@redhat.com>
To: Yura Pakhuchiy <pakhuchiy@gmail.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: L'\0' handling
Date: Thu, 08 Apr 2010 17:54:16 +0200	[thread overview]
Message-ID: <4BBDFC28.4080304@redhat.com> (raw)
In-Reply-To: <1270741172.2167.9.camel@yura-tl>

Yura Pakhuchiy wrote:
> У Чцв, 08/04/2010 у 17:22 +0200, Michael Stefaniuc піша:
>> Yura Pakhuchiy wrote:
>>> It looks like sparse do not understand constructions like L'\0'.
>> yepp, it doesn't. I have run into that problem 2 years ago. But for Wine
>> that is actually a "feature" as wide char/string literals are forbidden
>> aka cannot be used. Thus my interest in adding support for that in
>> sparse died.
> 
> Wine is not the only project which uses sparse. Sparse is broken for any
I'm a Wine developer and not a sparse developer. I was just saying that
I run into this problem in sparse, thought about fixing it but dumped
the idea and submitted instead patches to Wine to remove the wide
char/string literals.

> userspace program which includes wchar.h in Ubuntu with out supporting
> this.
I didn't assert that the feature shouldn't be implemented, just that it
is a known missing feature that the normal sparse consumer didn't need
until now.

bye
	michael
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-04-08 15:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08 14:59 L'\0' handling Yura Pakhuchiy
2010-04-08 15:22 ` Michael Stefaniuc
2010-04-08 15:39   ` Yura Pakhuchiy
2010-04-08 15:54     ` Michael Stefaniuc [this message]
2010-04-08 20:19       ` Christopher Li
     [not found]         ` <1270758815.2167.13.camel@yura-tl>
2010-04-08 20:46           ` Christopher Li
2010-04-08 20:58             ` Michael Stefaniuc
2010-04-08 23:18               ` Christopher Li
2010-04-09  8:57                 ` Michael Stefaniuc
2010-04-09 20:07                   ` Christopher Li
2010-04-09 20:28                     ` Michael Stefaniuc
2010-06-18  0:30                       ` Christopher Li

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=4BBDFC28.4080304@redhat.com \
    --to=mstefani@redhat.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=pakhuchiy@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.