Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder2.hal-mli.net!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <20121223171955.GB32535@ifeobi.illom.net>
References: <20121223171955.GB32535@ifeobi.illom.net>
Date: Mon, 24 Dec 2012 11:32:17 +1100
Subject: Re: Parsing files in python
From: Chris Angelico <rosuav@gmail.com>
To: python-list@python.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.1230.1356309147.29569.python-list@python.org>
Lines: 56
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:35420

On Mon, Dec 24, 2012 at 4:19 AM, Kene Meniru <kene.meniru@illom.org> wrote:
> Hello: I am writing a program that is made up of a collection of POV-Ray =
macros. POV-Ray is available at povray.org. It is a ray-tracing program tha=
t reads a scene description language (SDL) to create photo-realistic images=
. At this time my program (for modeling building information) is so huge th=
at I am finding it difficult managing the macros and I am not even near com=
pletion.

I love POV-Ray! Great software, but the input language does at times
lack something, so I'm not surprised that you're wanting a pre-parser.

> ------------possible user file content for parsing ------------
> // in the following the python interface program reads
> //+ the contents of the file "other.file" as if its content
> //+ were located at this point.
> include other.file
>
> //In the following the python interface makes "snap_size" a
> //+  global parameter
> declare snap_size =3D 10
>
>
> // In the following "buildingLevel" is a class that is
> //+  called and passed the parameters in parenthesis.
> buildingLevel("FirstLevel", 3000)
>
> // In the following "snapOffset" is a class that is
> //+  called and passed the parameters in parenthesis.
> snapOffset("Closet-S1_r1", "Closet-S2_r3", <0,0,0>)
> ------------end of user file content
>
> It should also be possible to include comments using double-slashes, etc.

Hmm. That's a fairly complex file format you have there. I wonder if
it'd be possible to use an actual language parser for it - for
instance, to make this a real Python program. You'd have to use # for
a comment rather than //, and vector syntax may be a problem, but for
the rest, you should be able to do it all with just one extra line at
the top:

from povray_macros import *

You then write all your macros in a file called povray_macros.py and
they'll be conveniently available. For instance:

def buildingLevel(name, altitude):
    print("... whatever POV-Ray code is needed ...")

Unfortunately POV-Ray doesn't seem to support reading from stdin, so
you can't simply pipe your program into the renderer. But you can do
it this way:

my_file_whatever_it_is.py >temp.pov
povray +Itemp.pov

ChrisA