From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pierre.weis@inria.fr>
Delivered-To: caml-list@yquem.inria.fr
Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78])
	by yquem.inria.fr (Postfix) with ESMTP id 64DCBBB91
	for <caml-list@yquem.inria.fr>; Fri, 28 Jan 2005 01:41:24 +0100 (CET)
Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35])
	by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id j0S0fNUw007749
	for <caml-list@yquem.inria.fr>; Fri, 28 Jan 2005 01:41:24 +0100
Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id BAA14205 for <caml-list@pauillac.inria.fr>; Fri, 28 Jan 2005 01:41:23 +0100 (MET)
Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.203])
	by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id j0S0fMqC007746
	for <caml-list@inria.fr>; Fri, 28 Jan 2005 01:41:23 +0100
Received: by wproxy.gmail.com with SMTP id 69so341385wra
        for <caml-list@inria.fr>; Thu, 27 Jan 2005 16:41:22 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
        b=KkBBjIT4USGvIldtwSf81rTRzOvIa9IDKK+D1hxxy48yU9ga1u4n2GEOKxbC9ylXqYEjNa+pMJECxAobuEe/rgUlezNqDNnHztNqvc30eSYifbE1WCUd/hnaA5siMD7MeqfnumqEcfPJaRe0rw74sffrcGQCqPHL3+l+Ue78Am8=
Received: by 10.54.24.8 with SMTP id 8mr83598wrx;
        Thu, 27 Jan 2005 16:41:21 -0800 (PST)
Received: by 10.54.5.8 with HTTP; Thu, 27 Jan 2005 16:41:21 -0800 (PST)
Message-ID: <875c7e0705012716411cb87bfb@mail.gmail.com>
Date: Thu, 27 Jan 2005 19:41:21 -0500
From: Chris King <colanderman@gmail.com>
Reply-To: Chris King <colanderman@gmail.com>
To: Jon Harrop <jon@jdh30.plus.com>
Subject: Re: [Caml-list] yacc style
Cc: "O'Caml Mailing List" <caml-list@inria.fr>
In-Reply-To: <200501272252.43720.jon@jdh30.plus.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <875c7e0705012712177a9e852@mail.gmail.com>
	 <200501272252.43720.jon@jdh30.plus.com>
X-Miltered: at nez-perce with ID 41F98A33.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)!
X-Miltered: at nez-perce with ID 41F98A32.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)!
X-Spam: no; 0.00; caml-list:01 wrote:01 parser:01 wrote:01 hash:01 ...:98 structures:01 checking:01 data:02 data:02 tree:02 tree:02 semantic:02 semantic:02 functional:02 
X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on yquem.inria.fr
X-Spam-Status: No, score=0.0 required=5.0 tests=RCVD_BY_IP autolearn=disabled 
	version=3.0.0
X-Spam-Level: 

On Fri, 28 Jan 2005 08:39:56 +1100, Erik de Castro Lopo
<ocaml-erikd@mega-nerd.com> wrote:
> Yes, normally the parser generates a parse tree which is then
> passed to the semantic analyser for semantic checking.

Okay, sounds good -- thanks!

On Thu, 27 Jan 2005 22:52:43 +0000, Jon Harrop <jon@jdh30.plus.com> wrote:
> May I ask what makes it difficult to use a functional style in your case?
> Perhaps it isn't as difficult as you think...

It's for performance reasons, mostly: the structure consists of a hash
table (to store user symbol definitions) and an array (for the actual
data).  It's easy enough to get the data in the form of a parse tree
and massage it into these structures afterwards; I was just wondering
if there was a more direct way.