Talk:Syntax checking/Parser - Revision history

Paulb: /* error classes */

2006-06-22T15:19:13Z

‎error classes

2006-06-20T20:46:24Z

‎error classes

2006-06-12T16:14:57Z

‎acex for parser application

2006-06-05T11:54:24Z

‎error classes

2006-06-05T11:18:17Z

‎acex for parser application

2006-05-23T15:01:30Z

acex for parser application

2006-05-21T22:36:31Z

‎find more than one error

2006-05-21T22:04:22Z

‎find more than one error

2006-05-21T17:30:07Z

‎find more than one error

2006-05-21T10:39:38Z

‎suggestion for implementation

← Older revision		Revision as of 15:19, 22 June 2006
Line 120:		Line 120:

	[[User:Chrigu\|Chrigu]] 22:46, 20 June 2006 (CEST)		[[User:Chrigu\|Chrigu]] 22:46, 20 June 2006 (CEST)
		+
		+	A lot of those features a very basic. I just sent Martin a brief description of `end_recover'. It simply was used to recover from an error and continue parsing. It called `clear_token' and would reset a state flag, used in error reporting, to allow errors to be generated and added to ERROR_HANDLER. In the case where `max_errors' was set, if the number of parse errors generated was greater that `max_errors', the state flag would not be reset.
		+
		+	`if_part_tuple' - I have no idea.
		+	`successful' - Indicates if parsing was successful
		+	`recoverable_parser' - Indicates if parser should recover from errors (For instance, syntax formatting tools should have this set to False)
		+	`leaf_list_as' - Was just needed for extracting location information from generated AS nodes. It was simply an emmpty initialized LEAF_AS_NODE. It's required for accessing AST_EIFFEL.complete_start_location/complete_end_location as AST_EIFFEL.start_location/end_location will ignore keywords. The full location information is required to create correct location information for errors.
		+
		+	As a note. The parser I gave you is only a reference. Do not use as your base for you implementation.
		+
		+	[[User:Paulb\|Paulb]] 17:19, 22 June 2006 (CEST)

← Older revision		Revision as of 20:46, 20 June 2006
Line 116:		Line 116:

	[[User:Maser\|maser]] 13:54, 5 June 2006 (CEST)		[[User:Maser\|maser]] 13:54, 5 June 2006 (CEST)
		+
		+	I have some problems: In EIFFEL_PARSER (generated by eiffel.y) are a lot of identifiers that are not defined (leaf_list_as: LEAF_AS_LIST;recoverable_parser, single_parser_type, successful: BOOLEAN;end_recover is do end;if_part_tuple: ?????). Where are they from? Should I inherit a class to solve that problem?
		+
		+	[[User:Chrigu\|Chrigu]] 22:46, 20 June 2006 (CEST)

@@ Line 102: / Line 102: @@
 == acex for parser application ==
-I've uploaded a [http://n.ethz.ch/student/luderm/parser.acex parser.acex] (why can't I upload it to the wiki?). You can also use parser.ecf file in Eiffel/parser/ in the current trunk as Manu pointed out.
+I've uploaded a [http://n.ethz.ch/student/luderm/parser.acex parser.acex] (Edit: removed, there's information on this topic in [[Syntax checking/Parser]]). You can also use parser.ecf file in Eiffel/parser/ in the current trunk as Manu pointed out.
 [[User:Maser|maser]] 17:01, 23 May 2006 (CEST)
 == error classes ==

← Older revision		Revision as of 11:54, 5 June 2006
Line 112:		Line 112:

	[[User:Chrigu\|Chrigu]] 13:18, 5 June 2006 (CEST)		[[User:Chrigu\|Chrigu]] 13:18, 5 June 2006 (CEST)
		+
		+
		+	It's decided in eiffel.y, as far as I know. There's a 'report_*' feature for each error class and in the eiffel.y the appropriate one is called with the right string from the EIFFEL_PARSER_ERRORS class.
		+
		+	[[User:Maser\|maser]] 13:54, 5 June 2006 (CEST)

← Older revision		Revision as of 11:18, 5 June 2006
Line 105:		Line 105:

	[[User:Maser\|maser]] 17:01, 23 May 2006 (CEST)		[[User:Maser\|maser]] 17:01, 23 May 2006 (CEST)
		+
		+
		+	== error classes ==
		+
		+	I've studied Paul's error classes. They all inherit of syntax_error. And they can be called by the eiffel_parser_error_reporter. But where you decide, which class you should choose to represent the error?
		+
		+	[[User:Chrigu\|Chrigu]] 13:18, 5 June 2006 (CEST)

← Older revision		Revision as of 15:01, 23 May 2006
Line 99:		Line 99:

	[[User:Chrigu\|Chrigu]] 12:39, 21 May 2006 (CEST)		[[User:Chrigu\|Chrigu]] 12:39, 21 May 2006 (CEST)
		+
		+	== acex for parser application ==
		+
		+	I've uploaded a [http://n.ethz.ch/student/luderm/parser.acex parser.acex] (why can't I upload it to the wiki?). You can also use parser.ecf file in Eiffel/parser/ in the current trunk as Manu pointed out.
		+
		+	[[User:Maser\|maser]] 17:01, 23 May 2006 (CEST)

@@ Line 75: / Line 75: @@
-Oh, you're right, everything's there, I just didn't see it.
+Oh, you're right, everything's there, I just didn't see it. I could create a new project based on that file and it seems like there's really a lot to do in the ERROR classes.
-[[User:Maser|maser]] 00:04, 22 May 2006 (CEST)
+[[User:Maser|maser]] 00:36, 22 May 2006 (CEST)
 == Interface to visualization group ==

@@ Line 68: / Line 68: @@
 [[User:Maser|maser]] 01:38, 21 May 2006 (CEST)
 If you take the configuration file parser.ecf in $EIFFEL_SRC/Eiffel/parser then it should include all you need.
 --[[User:Manus|manus]] 19:30, 21 May 2006 (CEST)
 == Interface to visualization group ==

← Older revision		Revision as of 17:30, 21 May 2006
Line 68:		Line 68:

	[[User:Maser\|maser]] 01:38, 21 May 2006 (CEST)		[[User:Maser\|maser]] 01:38, 21 May 2006 (CEST)
		+
		+	If you take the configuration file parser.ecf in $EIFFEL_SRC/Eiffel/parser then it should include all you need.
		+
		+	--[[User:Manus\|manus]] 19:30, 21 May 2006 (CEST)

	== Interface to visualization group ==		== Interface to visualization group ==