From: "Tim Harder (radhermit)" <radhermit@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in app-editors/xvile/files: vile-9.8h-flex.patch
Date: Tue, 28 Aug 2012 08:35:45 +0000 (UTC) [thread overview]
Message-ID: <20120828083545.E3434209EB@flycatcher.gentoo.org> (raw)
radhermit 12/08/28 08:35:45
Added: vile-9.8h-flex.patch
Log:
Version bump.
(Portage version: 2.2.0_alpha123/cvs/Linux x86_64)
Revision Changes Path
1.1 app-editors/xvile/files/vile-9.8h-flex.patch
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-editors/xvile/files/vile-9.8h-flex.patch?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-editors/xvile/files/vile-9.8h-flex.patch?rev=1.1&content-type=text/plain
Index: vile-9.8h-flex.patch
===================================================================
--- vile-9.8h/filters/filters.h
+++ vile-9.8h/filters/filters.h
@@ -200,27 +200,6 @@
#endif
#endif /* __GNUC__ */
-/*
- * 2003/5/20 - "new" flex 2.5.31:
- * workaround for "developers" who don't use compiler-warnings...
- * perhaps by the time "new" flex merits the term "beta", they'll fix this:
- */
-#if defined(FLEX_BETA)
-extern FILE *yyget_in (void);
-extern FILE *yyget_out (void);
-extern char *yyget_text (void);
-extern int yyget_debug (void);
-extern int yyget_leng (void);
-extern int yyget_lineno (void);
-extern int yylex_destroy (void);
-extern void yyset_debug (int bdebug);
-extern void yyset_in (FILE * in_str);
-extern void yyset_lineno (int line_number);
-extern void yyset_out (FILE * out_str);
-/* there's also warnings for unused 'yyunput()', but I don't see a fix */
-/* flex's skeleton includes <unistd.h> - no particular reason apparent */
-#endif
-
#define YY_NO_INPUT 1 /* get rid of 'input()' function */
/*
reply other threads:[~2012-08-28 8:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120828083545.E3434209EB@flycatcher.gentoo.org \
--to=radhermit@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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