From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7136 invoked by alias); 4 Nov 2009 21:07:58 -0000 Received: (qmail 7127 invoked by uid 22791); 4 Nov 2009 21:07:58 -0000 X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from aussmtpmrkps320.us.dell.com (HELO aussmtpmrkps320.us.dell.com) (143.166.224.254) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 04 Nov 2009 21:07:54 +0000 X-Loopcount0: from 12.110.134.31 Received: from unknown (HELO M31.equallogic.com) ([12.110.134.31]) by aussmtpmrkps320.us.dell.com with SMTP; 04 Nov 2009 15:07:53 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <19185.60662.189998.315630@pkoning-laptop.lab.equallogic.com> Date: Wed, 04 Nov 2009 21:07:00 -0000 From: Paul Koning To: tromey@redhat.com Cc: brobecker@adacore.com, james.pandavan@googlemail.com, gdb@sourceware.org Subject: Re: gdb v7.0 - user defined command's document section - space prefixed end References: <4AE7D19A.70600@googlemail.com> <20091103143305.GN4573@adacore.com> <4AF07D60.2020305@googlemail.com> <20091103194313.GS4573@adacore.com> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-11/txt/msg00043.txt.bz2 Excerpt of message (sent 4 November 2009) by Tom Tromey: > >>>>> "Joel" == Joel Brobecker writes: > > >> I noticed my scripts didn't work under v7.0 only when I saw this bug in > >> launchpad. I guess I am not the only one who has indented "ends" this way > >> :) > >> https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/461594 > > Joel> If you could maybe help us a little bit, and track down the author > Joel> of the patch that introduced the change of behavior, and then ask > Joel> him whether the change was intended? > > I think it may be because we allow multi-line python commands, and > python is sensitive to indentation. Yes, but "end" is not a Python keyword, so that isn't a reason to stop recognizing end. paul