9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: prem.mallappa@gmail.com, 9fans@9fans.net
Subject: Re: [9fans] plan9 lexer problem
Date: Mon, 10 Nov 2008 06:24:25 -0500	[thread overview]
Message-ID: <e13a176871e7765f064c3b5c885d4fec@quanstro.net> (raw)

> %{
> %}
>
> %%
> stop	print("Stop!! recieved\n");
> start	print("Start -> recieved\n");
> %%

the fix for this should be to add
#include <u.h>
#include <libc.h>

between %{ and %} but this doesn't work because
lex includes stdio.h before it processes %{ %}.
you'll need to write a shim, fixlex.c, that goes like this

#include <u.h>
#include <libc.h>
#include "lex.yy.c"

that is unless you want to dive into the lex source. :-)

- erik



             reply	other threads:[~2008-11-10 11:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-10 11:24 erik quanstrom [this message]
     [not found] <d60411c2783a8e0daa773573790ea2b5@quanstro.net>
2008-11-10 11:46 ` Prem Mallappa
  -- strict thread matches above, loose matches on Subject: below --
2008-11-10  9:56 prem

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=e13a176871e7765f064c3b5c885d4fec@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    --cc=prem.mallappa@gmail.com \
    /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).