From: Keith Packard <keithp@keithp.com>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: keithp@keithp.com, Git Mailing List <git@vger.kernel.org>
Subject: Re: parsecvs tool now creates git repositories
Date: Mon, 03 Apr 2006 15:19:13 -0700 [thread overview]
Message-ID: <1144102753.2303.121.camel@neko.keithp.com> (raw)
In-Reply-To: <1144083282.2303.102.camel@neko.keithp.com>
[-- Attachment #1: Type: text/plain, Size: 775 bytes --]
On Mon, 2006-04-03 at 09:54 -0700, Keith Packard wrote:
> On Mon, 2006-04-03 at 09:25 +0200, Jan-Benedict Glaw wrote:
>
> > -YFLAGS=-d
> > +YFLAGS=-d -l
> > +LFLAGS=-l
>
> Works for me too; thanks for the fix.
Well, -l *kinda* works; it places a limit on the maximum token size.
And, unlike 'lex', 'flex' places all input into the token buffer, even
if handled outside the usual lexer loop. So, my external function that
sucked up file contents was losing.
I switched it over to doing one-at-a-time reads from the input file, now
the external data function can directly use stdio. This eliminates all
calls to 'input' and 'unput' which should make it work for everyone now.
flex -- it's like lex, except less flexible.
--
keith.packard@intel.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-04-03 22:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-02 5:36 parsecvs tool now creates git repositories Keith Packard
2006-04-02 9:39 ` Jan-Benedict Glaw
2006-04-02 19:31 ` Jan-Benedict Glaw
2006-04-03 4:10 ` Keith Packard
2006-04-03 4:38 ` Linus Torvalds
2006-04-03 7:25 ` Jan-Benedict Glaw
2006-04-03 13:58 ` Erik Mouw
2006-04-03 16:54 ` Keith Packard
2006-04-03 22:19 ` Keith Packard [this message]
2006-04-03 14:03 ` Erik Mouw
2006-04-03 14:21 ` Jakub Narebski
2006-04-03 14:39 ` Keith Packard
2006-04-03 14:37 ` Keith Packard
2006-04-03 15:32 ` Jeff King
2006-04-04 0:55 ` Anand Kumria
2006-04-03 22:38 ` Martin Langhoff
2006-04-04 2:07 ` Keith Packard
2006-04-04 2:16 ` Martin Langhoff
2006-04-04 2:24 ` Keith Packard
2006-04-04 2:42 ` Martin Langhoff
2006-04-04 3:51 ` Keith Packard
2006-04-04 6:09 ` Junio C Hamano
[not found] <20060405174247.GA29758@blackbean.org>
[not found] ` <1144262498.2303.231.camel@neko.keithp.com>
2006-04-06 6:36 ` Fixes to parsecvs Keith Packard
2006-04-06 18:15 ` parsecvs tool now creates git repositories Jim Radford
2006-04-06 20:12 ` Keith Packard
2006-04-06 21:51 ` Martin Langhoff
2006-04-06 22:19 ` Keith Packard
2006-04-06 23:22 ` Martin Langhoff
2006-04-07 7:24 ` Keith Packard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1144102753.2303.121.camel@neko.keithp.com \
--to=keithp@keithp.com \
--cc=git@vger.kernel.org \
--cc=jbglaw@lug-owl.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).