From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5855 invoked by alias); 18 Dec 2006 15:35:51 -0000 Received: (qmail 5842 invoked by uid 22791); 18 Dec 2006 15:35:50 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 18 Dec 2006 15:35:42 +0000 Received: (qmail 22749 invoked from network); 18 Dec 2006 15:35:41 -0000 Received: from unknown (HELO 172.16.unknown.plus.ru) (vladimir@127.0.0.2) by mail.codesourcery.com with ESMTPA; 18 Dec 2006 15:35:41 -0000 From: Vladimir Prus To: gdb@sources.redhat.com Subject: MI fine-grained versioning Date: Mon, 18 Dec 2006 15:35:00 -0000 User-Agent: KMail/1.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200612181835.34025.vladimir@codesourcery.com> 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: 2006-12/txt/msg00166.txt.bz2 At the moment, MI does not have any mechanism to announce supported features. For example, I have a patch to add "frozen" variable objects. To support such feature in a backward-compatible fashion, the frontend must know if that features is supported by the given gdb binary. Using version number is not very reliable -- for example if you use the CVS state of gdb, the version number is not yet bumped. Yet another approach is to "detect" presence of feature by trying some commands, or by trying commands with some new options, or by constructing more contrived test cases. However that's troublesome. How about adding new MI command that returnes list of supported fine-grained features. For example: -list-features ^done,result=["frozen_variables","info_path_expression"] The MI manual would contain a section listing all feature names and briefly documenting them. Comments? - Volodya