From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3196 invoked by alias); 11 Jun 2008 19:06:49 -0000 Received: (qmail 3178 invoked by uid 22791); 11 Jun 2008 19:06:49 -0000 X-Spam-Check-By: sourceware.org Received: from mtaout4.012.net.il (HELO mtaout4.012.net.il) (84.95.2.10) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 11 Jun 2008 19:06:27 +0000 Received: from HOME-C4E4A596F7 ([80.230.28.131]) by i_mtaout4.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0K2B00ATXCFNDH91@i_mtaout4.012.net.il> for gdb-patches@sources.redhat.com; Wed, 11 Jun 2008 22:21:24 +0300 (IDT) Date: Wed, 11 Jun 2008 22:36:00 -0000 From: Eli Zaretskii Subject: Re: [mi, doc] mention escape sequences In-reply-to: <200806111807.25820.vladimir@codesourcery.com> X-012-Sender: halo1@inter.net.il To: Vladimir Prus Cc: gdb-patches@sources.redhat.com Reply-to: Eli Zaretskii Message-id: References: <200806111807.25820.vladimir@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-06/txt/msg00226.txt.bz2 > From: Vladimir Prus > Date: Wed, 11 Jun 2008 18:07:25 +0400 > > Note that parse_escape function supports more than C language escape > sequences, it seems, but given that the function has no comments on > those sequences, and given that manual does not say anything about > that either, I don't feel like reverse-engineering the code to > document the exact rules. "As in C" as sufficient, I think, for MI > manual. Maybe not all exact rules, but a single example would be good, I think. After all ``escape sequences'' is a heavily overloaded term, even with the "C" qualifier, and without an example, the reader might be left in doubt. > Escape sequences are not allowed in @var{non-blank-sequence}. How do you mean ``not allowed''? Perhaps you mean ``not interpreted'', i.e. output verbatim?