Ethereal-dev: RE: [ethereal-dev] initial X11 dissector close to completion, but...

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: "Graham Bloice" <graham.bloice@xxxxxxxxxxxxx>
Date: Mon, 12 Jun 2000 16:35:45 +0100
This means that I'll have to install Perl to build on Win32.  More disk
space !

GB

> -----Original Message-----
> From: owner-ethereal-dev@xxxxxxxx [mailto:owner-ethereal-dev@xxxxxxxx]On
> Behalf Of Gilbert Ramirez
> Sent: 12 June 2000 16:12
> To: Guy Harris
> Cc: Christophe Tronche; ethereal-dev@xxxxxxxx
> Subject: Re: [ethereal-dev] initial X11 dissector close to completion,
> but...
>
>
> On Mon, Jun 12, 2000 at 04:24:08AM -0500, Guy Harris wrote:
> >
> >
> > On Sun, Jun 04, 2000 at 05:05:42PM +0200, Christophe Tronche wrote:
> > > I've got a lot of header fields (about 370 of them). To keep things
> > > manageable, I've put them in a text file, with a short Perl script
> > > (very specific to my needs) to create the register info and variable
> > > declarations in two .h files, then #included in the packet-x11.c file
> > > (I remember having seen this kind of things discussed before).
> >
> > What does the Perl script use as input?
> >
> > People may well add more fields to the X11 dissector if they add support
> > for X11 extensions, so the script might be useful to others.
>
> I wouldn't mind using Perl as another part of our build process. We use
> it to create the man pages. If we decide to use Perl for other files,
> I could get rid of "rdps" and use a Perl script. Also, I'm working on
> a re-do of the NCP dissector. It uses a table of information and a Python
> script to generate the C code. If we decide to use perl, I'll convert
> the NCP script to Perl.
>
> --gilbert
>
>