Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1D5A9DFFC for ; Mon, 1 Oct 2012 12:08:10 +0000 (UTC) Received: (qmail 57278 invoked by uid 500); 1 Oct 2012 12:08:09 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 57038 invoked by uid 500); 1 Oct 2012 12:08:08 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 57026 invoked by uid 99); 1 Oct 2012 12:08:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Oct 2012 12:08:08 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.220.175] (HELO mail-vc0-f175.google.com) (209.85.220.175) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Oct 2012 12:08:02 +0000 Received: by vcqp1 with SMTP id p1so5450515vcq.6 for ; Mon, 01 Oct 2012 05:07:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=BnxAK1PSo+HLXU0YoK+FqR+YfywdHOCd9z0PUL/L+W8=; b=atzdZ5jJaSTEgny/21vXi4f3/4G6/BX37bKdW78Ca3BwfA7oQY8ex7qp8kwWbo7ggo 5EcctVXMPt1xLJJNi+35zCZ2azeWHq2oHa3sDj8lL7fIhMFkLh7qbNKg7F99ZxUhQEWg lDu6wUwdXIy8cdpRU706KKdvkcCbzO749rrnzLbu/y53UH8WHx2pwQ3MJcq3QO9bY1+E IurFEzjZINl2vH5zvIe5afKY4PibKsaqgwrfKJDIeiEKEAoTIeFE73nE4U7xl9ZjQ07x b8x0FRuUOfdds6jutdL6Bcd6588RZNSY8MY8zefCDgTlpTVJBerTf9X3+Pr80l3YpFS3 ZLsQ== MIME-Version: 1.0 Received: by 10.220.148.134 with SMTP id p6mr3072371vcv.3.1349093261399; Mon, 01 Oct 2012 05:07:41 -0700 (PDT) Received: by 10.58.239.164 with HTTP; Mon, 1 Oct 2012 05:07:41 -0700 (PDT) In-Reply-To: <20121001075133.961363dcexlalw3p@www.teotigraphix.com> References: <20120928151647.674724k5xvsi4lgf@www.teotigraphix.com> <20121001063216.338788433szk89bl@www.teotigraphix.com> <20121001072154.137821zpgpccvp3m@www.teotigraphix.com> <20121001075133.961363dcexlalw3p@www.teotigraphix.com> Date: Mon, 1 Oct 2012 14:07:41 +0200 Message-ID: Subject: Re: Flex CodeScape ... From: Roland Zwaga To: flex-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=f46d043be1d49d55b604cafe4019 X-Gm-Message-State: ALoCoQlIIxiUOEb6kcDe4xhDfZ14bN0/Eul7Lbs9gN+QQURKvxPsV5xZBN1NTVGZjpHJiGYRpj7n X-Virus-Checked: Checked by ClamAV on apache.org --f46d043be1d49d55b604cafe4019 Content-Type: text/plain; charset=ISO-8859-1 > > Yeah took a look at the PDF, there are some things that need to be thought > about. I'm not really at the point where I could even begin to think about > this part. > > Hopefully others might take an interest when the framework is up and could > help contribute then. > > BTW the "framework" here uses the parser to load source files and swcs, > create the AST nodes and IDefinitions. > > Once the parsing is done a processor takes all the compilation units and > sorts all member data, meta data into an accessor map API. From there > processing is done to resolve inherited comments, accessor get-set pairs > and various other things. > > At this point, anything is possible, using the accessor map dependencies > are set and it's just a matter of finessing the API to create the output > you want. > > IE With the first iteration here I have created the asdoc HTML API docs > using Velocity templates. Works very fast. I am parsing and outputting the > spark and framework html in 35 seconds. Hey Mike, do you think your framework could also form a basis for static analysis tools such as FlexPMD/CPD et al? If the parsing is so much faster than perhaps these existing tools could be re-written to use the new compiler. I myself know absolutely nothing about static code analysis, but perhaps folks on the list here do and leveraging your existing work could be beneficial. cheers, Roland --f46d043be1d49d55b604cafe4019--