From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4668 invoked by alias); 14 Apr 2006 18:30:34 -0000 Received: (qmail 4660 invoked by uid 22791); 14 Apr 2006 18:30:33 -0000 X-Spam-Check-By: sourceware.org Received: from nitzan.inter.net.il (HELO nitzan.inter.net.il) (192.114.186.20) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 14 Apr 2006 18:30:31 +0000 Received: from HOME-C4E4A596F7 (IGLD-83-130-214-179.inter.net.il [83.130.214.179]) by nitzan.inter.net.il (MOS 3.7.3-GA) with ESMTP id DDG73436 (AUTH halo1); Fri, 14 Apr 2006 21:30:28 +0300 (IDT) Date: Fri, 14 Apr 2006 19:19:00 -0000 Message-Id: From: Eli Zaretskii To: "Jim Blandy" CC: gdb@sourceware.org In-reply-to: <8f2776cb0604141103p2adc9632j4b85af5fd72d8dc@mail.gmail.com> (jimb@red-bean.com) Subject: Re: printing wchar_t* Reply-to: Eli Zaretskii References: <200604141257.41690.ghost@cs.msu.su> <20060414130527.GA12955@nevyn.them.org> <20060414141640.GA14789@nevyn.them.org> <8f2776cb0604141018h33e7954j2a85784d6e1ba5ba@mail.gmail.com> <8f2776cb0604141103p2adc9632j4b85af5fd72d8dc@mail.gmail.com> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-04/txt/msg00204.txt.bz2 > Date: Fri, 14 Apr 2006 11:03:38 -0700 > From: "Jim Blandy" > Cc: gdb@sourceware.org > > > > I don't think it's worth complicating the syntax for searching for a > > > zero terminator in order to allow one to search for an arbitrary > > > terminator. > > > > Then how will you find the zero terminator? With wcslen? That is > > only good for wchar_t strings, not for arbitrary integer arrays. And > > I thought Daniel was suggesting something more general than just > > wchar_t arrays. > > He is. I am, too. Just search for elements equal to zero. How is this different or more complex than searching for elements that are equal to some other constant value? > That said, I don't even think we should have a separate command for > setting the terminating value for @@. I think we should wait until > someone has a need for it arising out of a real-life use case, not a > design conversation. What Daniel suggested didn't come from a clear-cut real-life use-case, either.