Lifted the ';'-after-events rule, though it can still be present. C++ allows it for functions, so this feels like the best solution regarding consistency.. I'm not even sure am I going overboard with this kind of stuff

Mon, 16 Jul 2012 04:33:09 +0300

author
Teemu Piippo <crimsondusk64@gmail.com>
date
Mon, 16 Jul 2012 04:33:09 +0300
changeset 31
ad027ea58097
parent 30
6c4efed2dbdd
child 32
d11a034aabfd

Lifted the ';'-after-events rule, though it can still be present. C++ allows it for functions, so this feels like the best solution regarding consistency.. I'm not even sure am I going overboard with this kind of stuff

parser.cxx file | annotate | diff | comparison | revisions
--- a/parser.cxx	Mon Jul 16 04:26:27 2012 +0300
+++ b/parser.cxx	Mon Jul 16 04:33:09 2012 +0300
@@ -191,7 +191,8 @@
 			w->Write (dataheader);
 			g_CurMode = MODE_TOPLEVEL;
 			
-			MustNext (";");
+			if (!PeekNext().compare (";"))
+				MustNext (";");
 			continue;
 		}
 		// Check global variables

mercurial