From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15515 invoked by alias); 6 Dec 2006 23:44:55 -0000 Received: (qmail 15358 invoked by uid 48); 6 Dec 2006 23:44:43 -0000 Date: Wed, 06 Dec 2006 23:51:00 -0000 Message-ID: <20061206234443.15357.qmail@sourceware.org> From: "fche at redhat dot com" To: systemtap@sources.redhat.com In-Reply-To: <20061206232852.3671.mmlnx@us.ibm.com> References: <20061206232852.3671.mmlnx@us.ibm.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug translator/3671] Support array size declarations X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2006-q4/txt/msg00623.txt.bz2 ------- Additional Comments From fche at redhat dot com 2006-12-06 23:44 ------- What has been holding us back is the lack of a proposed syntax. OK, here is a simple and intuitive one: global array[size] Of course, this [size] usage may look different from actual key-tuple-based indexing, but I suspect this would be OK. It would be easy to implement. The vardecl class would have to get a maxsize field. The parser::parse_global function would have to look for [literal_number] set the field. Last, the translator would have to arrange to pass the new field to mapvar::init. -- http://sourceware.org/bugzilla/show_bug.cgi?id=3671 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.