EiffelStudio: an EiffelSoftware project - User contributions [en]

Talk:Syntax checking/Parser

2006-06-20T20:46:24Z

Chrigu: /* error classes */

==find more than one error==
As far as I've seen, the Parser throws an ERROR as soon as it doesn't like something in the source, which aborts parsing. The found error is in the SHARED_ERROR_HANDLER's error_list (I've never seen more than one error in there, why is it a list anyway?). Has anybody found a way to tell the parser to parse the whole file?

[[User:Maser|maser]] 14:55, 17 May 2006 (CEST)

Hmmm... I don't know how to get all the errors with one call. But you haven't to parse the whole file, so you can parse piecewise and if an error occurs, you have to parse after the string that occurs the error. This is a way to get all errors, it's complicated, but it should work!?

[[User:Chrigu|Chrigu]] 17:19, 17 May 2006 (CEST)

Actually read http://www.gobosoft.com/eiffel/gobo/geyacc/error.html for more info on how modifying `eiffel.y' to recover from error and therefore detect more than one error at a time.

--[[User:Manus|manus]] 18:10, 17 May 2006 (CEST)

Chrigu: How exactly do you parse piecewise? Though it wouldn't solve the problem because there can be several errors in one piece.
Manu: Thanks for the hint! Looks very promising!

[[User:Maser|maser]] 22:55, 17 May 2006 (CEST)

Maser: Couldn't we read several strings of the file and use parse_with_string instead of parse? I'm not sure...

[[User:Chrigu|Chrigu]] 15:52, 18 May 2006 (CEST)

Chrigu: A normal EIFFEL_PARSER accepts just classes, but you can use set_expression_parser (or some other `Parser type setting' feature) to create a parser that parses Eiffel expressions (I knew I had seen something like that before, but couldn't find it yesterday). But changing the eiffel.y file seems like a better solution. Maybe we should use expression and/or feature parsers while checking if a previously found error has been corrected by the user (I assume parsing just one expression is pretty fast).

I've looked through the documentation of gayacc and I think it shouldn't be too difficult to change eiffel.y to our needs, the file's size will probably bethe biggest problem.

[[User:Maser|maser]] 16:31, 18 May 2006 (CEST)

Everyone, I've sent Martin something that I worked on a couple a months ago. It's be no means finished or polished. It got put on the back burner because I need to work on other parts of EiffelEnvision. I also do not think it is the most recent version but I will need to check at home for the latest bits.

Basically I sent him what I started implementing for a recoverable parser in the new EiffelEnvision editor. It supported recovering from errors (more complex cannot be support with ease because it's hard to find a recoverable token - Eiffel does not have mandatory end-of-statement tokens like C/C++/C#), precise error/warning reporting (a real message stating excatly what is wrong) and absolute error positions (if you notice EiffelStudio does not always give the exact error location.)

One thing that I started doing, which you guys are going to need to address too, is error/warning spans. It would be nice if the error reporting indicated the start and end coordinates (x1, y1 - x2, y2) of the error, without draining performance.

The parser is common to EiffelStudio/Compiler, EiffelEnvision and a number of internal tools, which is something you need to be aware of. That means do not add any references to anything related to the compiler or EiffelStudio. The parser itself is a stand-alone cluster.

Creating a recoverable parser is hard and placement of those error token is a black art (that's what O'Reilly say and I agree)! Good luck :)

--[[User:Paulb|Paulb]] 17:59, 18 May 2006 (CEST)

Thanks a lot for the code, Paul!

I quickly looked through it and I'll summarize how (I think) it works: eiffel.y is extended is modified like described on the page Manu mentioned (according to Paul it contains bugs because he didn't finish it, and it isn't up to date because eiffel.y was extended to support new language features), so that it reports multiple errors (and stores them in SHARED_ERROR_HANDLER.error_list). It's about a thousand lines longer than the version in the repository. Additionally, there are new ERROR classes that describe the found syntax errors and some helper classes. Paul also mentioned that he made changes to EIFFEL_PARSER_SKELETON, but he couldn't find them.

[[User:Maser|maser]] 20:15, 18 May 2006 (CEST)

The ERROR classes in Paul's code aren't compatible with the ones in the current version (mainly the versions of SYNTAX_ERROR and SYNTAX_MESSAGE are quite different).

[[User:Maser|maser]] 00:54, 19 May 2006 (CEST)

That's correct. The existing error classes did not support everything they needed to support, so I reworte them. If you actually look at the parser error/warning classes in the parser cluster (not EiffelStudio's error classes) you'll see that the warning class is not even implemented!

As I said, the parser is a stand-alone library. The parser cluster was only moved under Src/Eiffel for ease to users to check out and compile Eiffel. In that respect you should just create an application that uses the parser library, as I did. I then sent a generated error string, from the error classes, to the the command-line shell.

[[User:Paulb|Paulb]] 22:14, 20 May 2006 (CEST)

I'm not sure if I understand what you mean. Basically, I should be able to take just the parser cluster and write a program that parses Eiffel files? But that's not possible, because EIFFEL_PARSER_SKELETON inherits from SHARED_ERROR_HANDLER, which is in the compiler cluster. Also, the error/warning classes in the parser cluster aren't used in ES, only the ones in the compiler cluster. I'd really like to create an application that uses the parser library, but I don't understand how it's going to work without the compiler cluster.

[[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)

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:36, 22 May 2006 (CEST)

== Interface to visualization group ==

As the parser produces ERROR objects and they contain information about position and description of the error and stores them in SHARED_ERROR_HANDLER.error_list, I suggest we use this as interface to exchange the data between the parser and visualisation groups.

[[User:Maser|maser]] 16:43, 18 May 2006 (CEST)

I didn't look into it too much, but the ERROR classes can do some stuff with TEXT_FORMATTERs (several elements of the GUI inherit from TEXT_FORMATTER) which could be useful to display information about the ERROR.

[[User:Maser|maser]] 02:22, 21 May 2006 (CEST)

== suggestion for implementation ==

I've added a suggestion how to implement our changes. How bad is it? Comments? Improvements?

[[User:Maser|maser]] 16:35, 19 May 2006 (CEST)

It's not bad, it sounds good ;)

[[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] (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 ==

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)

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)

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)

Talk:Syntax checking/Parser

2006-06-05T11:18:17Z

Chrigu: /* acex for parser application */

==find more than one error==
As far as I've seen, the Parser throws an ERROR as soon as it doesn't like something in the source, which aborts parsing. The found error is in the SHARED_ERROR_HANDLER's error_list (I've never seen more than one error in there, why is it a list anyway?). Has anybody found a way to tell the parser to parse the whole file?

[[User:Maser|maser]] 14:55, 17 May 2006 (CEST)

Hmmm... I don't know how to get all the errors with one call. But you haven't to parse the whole file, so you can parse piecewise and if an error occurs, you have to parse after the string that occurs the error. This is a way to get all errors, it's complicated, but it should work!?

[[User:Chrigu|Chrigu]] 17:19, 17 May 2006 (CEST)

Actually read http://www.gobosoft.com/eiffel/gobo/geyacc/error.html for more info on how modifying `eiffel.y' to recover from error and therefore detect more than one error at a time.

--[[User:Manus|manus]] 18:10, 17 May 2006 (CEST)

Chrigu: How exactly do you parse piecewise? Though it wouldn't solve the problem because there can be several errors in one piece.
Manu: Thanks for the hint! Looks very promising!

[[User:Maser|maser]] 22:55, 17 May 2006 (CEST)

Maser: Couldn't we read several strings of the file and use parse_with_string instead of parse? I'm not sure...

[[User:Chrigu|Chrigu]] 15:52, 18 May 2006 (CEST)

Chrigu: A normal EIFFEL_PARSER accepts just classes, but you can use set_expression_parser (or some other `Parser type setting' feature) to create a parser that parses Eiffel expressions (I knew I had seen something like that before, but couldn't find it yesterday). But changing the eiffel.y file seems like a better solution. Maybe we should use expression and/or feature parsers while checking if a previously found error has been corrected by the user (I assume parsing just one expression is pretty fast).

I've looked through the documentation of gayacc and I think it shouldn't be too difficult to change eiffel.y to our needs, the file's size will probably bethe biggest problem.

[[User:Maser|maser]] 16:31, 18 May 2006 (CEST)

Everyone, I've sent Martin something that I worked on a couple a months ago. It's be no means finished or polished. It got put on the back burner because I need to work on other parts of EiffelEnvision. I also do not think it is the most recent version but I will need to check at home for the latest bits.

Basically I sent him what I started implementing for a recoverable parser in the new EiffelEnvision editor. It supported recovering from errors (more complex cannot be support with ease because it's hard to find a recoverable token - Eiffel does not have mandatory end-of-statement tokens like C/C++/C#), precise error/warning reporting (a real message stating excatly what is wrong) and absolute error positions (if you notice EiffelStudio does not always give the exact error location.)

One thing that I started doing, which you guys are going to need to address too, is error/warning spans. It would be nice if the error reporting indicated the start and end coordinates (x1, y1 - x2, y2) of the error, without draining performance.

The parser is common to EiffelStudio/Compiler, EiffelEnvision and a number of internal tools, which is something you need to be aware of. That means do not add any references to anything related to the compiler or EiffelStudio. The parser itself is a stand-alone cluster.

Creating a recoverable parser is hard and placement of those error token is a black art (that's what O'Reilly say and I agree)! Good luck :)

--[[User:Paulb|Paulb]] 17:59, 18 May 2006 (CEST)

Thanks a lot for the code, Paul!

I quickly looked through it and I'll summarize how (I think) it works: eiffel.y is extended is modified like described on the page Manu mentioned (according to Paul it contains bugs because he didn't finish it, and it isn't up to date because eiffel.y was extended to support new language features), so that it reports multiple errors (and stores them in SHARED_ERROR_HANDLER.error_list). It's about a thousand lines longer than the version in the repository. Additionally, there are new ERROR classes that describe the found syntax errors and some helper classes. Paul also mentioned that he made changes to EIFFEL_PARSER_SKELETON, but he couldn't find them.

[[User:Maser|maser]] 20:15, 18 May 2006 (CEST)

The ERROR classes in Paul's code aren't compatible with the ones in the current version (mainly the versions of SYNTAX_ERROR and SYNTAX_MESSAGE are quite different).

[[User:Maser|maser]] 00:54, 19 May 2006 (CEST)

That's correct. The existing error classes did not support everything they needed to support, so I reworte them. If you actually look at the parser error/warning classes in the parser cluster (not EiffelStudio's error classes) you'll see that the warning class is not even implemented!

As I said, the parser is a stand-alone library. The parser cluster was only moved under Src/Eiffel for ease to users to check out and compile Eiffel. In that respect you should just create an application that uses the parser library, as I did. I then sent a generated error string, from the error classes, to the the command-line shell.

[[User:Paulb|Paulb]] 22:14, 20 May 2006 (CEST)

I'm not sure if I understand what you mean. Basically, I should be able to take just the parser cluster and write a program that parses Eiffel files? But that's not possible, because EIFFEL_PARSER_SKELETON inherits from SHARED_ERROR_HANDLER, which is in the compiler cluster. Also, the error/warning classes in the parser cluster aren't used in ES, only the ones in the compiler cluster. I'd really like to create an application that uses the parser library, but I don't understand how it's going to work without the compiler cluster.

[[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)

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:36, 22 May 2006 (CEST)

== Interface to visualization group ==

As the parser produces ERROR objects and they contain information about position and description of the error and stores them in SHARED_ERROR_HANDLER.error_list, I suggest we use this as interface to exchange the data between the parser and visualisation groups.

[[User:Maser|maser]] 16:43, 18 May 2006 (CEST)

I didn't look into it too much, but the ERROR classes can do some stuff with TEXT_FORMATTERs (several elements of the GUI inherit from TEXT_FORMATTER) which could be useful to display information about the ERROR.

[[User:Maser|maser]] 02:22, 21 May 2006 (CEST)

== suggestion for implementation ==

I've added a suggestion how to implement our changes. How bad is it? Comments? Improvements?

[[User:Maser|maser]] 16:35, 19 May 2006 (CEST)

It's not bad, it sounds good ;)

[[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)

== 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)

Talk:Syntax checking/Parser

2006-05-21T10:39:38Z

Chrigu: /* suggestion for implementation */

==find more than one error==
As far as I've seen, the Parser throws an ERROR as soon as it doesn't like something in the source, which aborts parsing. The found error is in the SHARED_ERROR_HANDLER's error_list (I've never seen more than one error in there, why is it a list anyway?). Has anybody found a way to tell the parser to parse the whole file?

[[User:Maser|maser]] 14:55, 17 May 2006 (CEST)

Hmmm... I don't know how to get all the errors with one call. But you haven't to parse the whole file, so you can parse piecewise and if an error occurs, you have to parse after the string that occurs the error. This is a way to get all errors, it's complicated, but it should work!?

[[User:Chrigu|Chrigu]] 17:19, 17 May 2006 (CEST)

Actually read http://www.gobosoft.com/eiffel/gobo/geyacc/error.html for more info on how modifying `eiffel.y' to recover from error and therefore detect more than one error at a time.

--[[User:Manus|manus]] 18:10, 17 May 2006 (CEST)

Chrigu: How exactly do you parse piecewise? Though it wouldn't solve the problem because there can be several errors in one piece.
Manu: Thanks for the hint! Looks very promising!

[[User:Maser|maser]] 22:55, 17 May 2006 (CEST)

Maser: Couldn't we read several strings of the file and use parse_with_string instead of parse? I'm not sure...

[[User:Chrigu|Chrigu]] 15:52, 18 May 2006 (CEST)

Chrigu: A normal EIFFEL_PARSER accepts just classes, but you can use set_expression_parser (or some other `Parser type setting' feature) to create a parser that parses Eiffel expressions (I knew I had seen something like that before, but couldn't find it yesterday). But changing the eiffel.y file seems like a better solution. Maybe we should use expression and/or feature parsers while checking if a previously found error has been corrected by the user (I assume parsing just one expression is pretty fast).

I've looked through the documentation of gayacc and I think it shouldn't be too difficult to change eiffel.y to our needs, the file's size will probably bethe biggest problem.

[[User:Maser|maser]] 16:31, 18 May 2006 (CEST)

Everyone, I've sent Martin something that I worked on a couple a months ago. It's be no means finished or polished. It got put on the back burner because I need to work on other parts of EiffelEnvision. I also do not think it is the most recent version but I will need to check at home for the latest bits.

Basically I sent him what I started implementing for a recoverable parser in the new EiffelEnvision editor. It supported recovering from errors (more complex cannot be support with ease because it's hard to find a recoverable token - Eiffel does not have mandatory end-of-statement tokens like C/C++/C#), precise error/warning reporting (a real message stating excatly what is wrong) and absolute error positions (if you notice EiffelStudio does not always give the exact error location.)

One thing that I started doing, which you guys are going to need to address too, is error/warning spans. It would be nice if the error reporting indicated the start and end coordinates (x1, y1 - x2, y2) of the error, without draining performance.

The parser is common to EiffelStudio/Compiler, EiffelEnvision and a number of internal tools, which is something you need to be aware of. That means do not add any references to anything related to the compiler or EiffelStudio. The parser itself is a stand-alone cluster.

Creating a recoverable parser is hard and placement of those error token is a black art (that's what O'Reilly say and I agree)! Good luck :)

--[[User:Paulb|Paulb]] 17:59, 18 May 2006 (CEST)

Thanks a lot for the code, Paul!

I quickly looked through it and I'll summarize how (I think) it works: eiffel.y is extended is modified like described on the page Manu mentioned (according to Paul it contains bugs because he didn't finish it, and it isn't up to date because eiffel.y was extended to support new language features), so that it reports multiple errors (and stores them in SHARED_ERROR_HANDLER.error_list). It's about a thousand lines longer than the version in the repository. Additionally, there are new ERROR classes that describe the found syntax errors and some helper classes. Paul also mentioned that he made changes to EIFFEL_PARSER_SKELETON, but he couldn't find them.

[[User:Maser|maser]] 20:15, 18 May 2006 (CEST)

The ERROR classes in Paul's code aren't compatible with the ones in the current version (mainly the versions of SYNTAX_ERROR and SYNTAX_MESSAGE are quite different).

[[User:Maser|maser]] 00:54, 19 May 2006 (CEST)

That's correct. The existing error classes did not support everything they needed to support, so I reworte them. If you actually look at the parser error/warning classes in the parser cluster (not EiffelStudio's error classes) you'll see that the warning class is not even implemented!

As I said, the parser is a stand-alone library. The parser cluster was only moved under Src/Eiffel for ease to users to check out and compile Eiffel. In that respect you should just create an application that uses the parser library, as I did. I then sent a generated error string, from the error classes, to the the command-line shell.

[[User:Paulb|Paulb]] 22:14, 20 May 2006 (CEST)

I'm not sure if I understand what you mean. Basically, I should be able to take just the parser cluster and write a program that parses Eiffel files? But that's not possible, because EIFFEL_PARSER_SKELETON inherits from SHARED_ERROR_HANDLER, which is in the compiler cluster. Also, the error/warning classes in the parser cluster aren't used in ES, only the ones in the compiler cluster. I'd really like to create an application that uses the parser library, but I don't understand how it's going to work without the compiler cluster.

[[User:Maser|maser]] 01:38, 21 May 2006 (CEST)

== Interface to visualization group ==

As the parser produces ERROR objects and they contain information about position and description of the error and stores them in SHARED_ERROR_HANDLER.error_list, I suggest we use this as interface to exchange the data between the parser and visualisation groups.

[[User:Maser|maser]] 16:43, 18 May 2006 (CEST)

I didn't look into it too much, but the ERROR classes can do some stuff with TEXT_FORMATTERs (several elements of the GUI inherit from TEXT_FORMATTER) which could be useful to display information about the ERROR.

[[User:Maser|maser]] 02:22, 21 May 2006 (CEST)

== suggestion for implementation ==

I've added a suggestion how to implement our changes. How bad is it? Comments? Improvements?

[[User:Maser|maser]] 16:35, 19 May 2006 (CEST)

It's not bad, it sounds good ;)

[[User:Chrigu|Chrigu]] 12:39, 21 May 2006 (CEST)

Talk:Syntax checking/Parser

2006-05-18T13:52:54Z

Chrigu: /* find more than one error */

Talk:Syntax checking/Parser

2006-05-18T13:52:41Z

Chrigu: /* find more than one error */

Talk:Syntax checking/Parser

2006-05-17T15:19:56Z

Chrigu:

Talk:Syntax checking/Parser

2006-05-17T15:19:25Z

Chrigu: /* find more than one error */

Syntax checking/Parser

2006-05-17T12:35:25Z

Chrigu:

[[Syntax_checking|back to Syntax checking page]]

==Important Classes==

====EIFFEL_PARSER====
* inherits from EIFFEL_PARSER_SKELETON (where the features parse, parse_string, make_with_factory are implemented)
* make_with_factory (a_factory: AST_FACTORY): give argument of type AST_NULL_FACTORY (inherits from AST_FACTORY)
* parse (a_file: KL_BINARY_INPUT_FILE) and parse_from_string (a_string: STRING): Both save the results in match_list: LEAF_AS_LIST.
====CLASS_AS====
* AST of a class
====ERROR====
* deferred; superclass of all error types like EIFFEL_ERROR or SYNTAX_ERROR
* features line, column: INTEGER give location of error
====ERROR_HANDLER====
* feature error_list: ERROR is a list of errors found by the parser
====SHARED_ERROR_HANDLER====
* singleton used by all relevant classes

====EIFFEL_CLASS_C====
* features build_ast and parse_ast show how the parser can be used.

Syntax checking

2006-05-17T12:21:25Z

Chrigu:

[[Category:Projects]]
[[Category:Editor]]
=Overview=
The aim of this project is to provide adequate, but non intrusive feedback to user about syntax errors. This is done by checking syntax as you type and underlining syntax errors by the well knwon wavy red line. Furthermore, error descriptions and possible solutions should be provided.

The Project is named '''SynChé''', which is a combination of syntax and checking.
The ''é'' at the end is important, as a cool name needs either a recursive acronym or a special character from a non English language.

=Software Requirement Specification (SRS)=
You can find our SRS [[Syntax_checking/SRS|here]]

=Groups=

* [[Syntax_checking/Visualisation|Visualisation]]
* [[Syntax_checking/Parser|Parser]]

=Milestones=

==M1: April 25th==
* Get home-grown EiffelStudio up and running.

==M2: May 2nd==
* '''Put your name in this Wiki!'''
* Analyse source code to certain degree, so discussion about interfaces between parser and visual is possible

==M3: May 9th==
* SRS written
* Overview of relevant classes (BON diagram or more)
* Further Project Milestones specified, based on SRS and knowledge about code

== May 12th ==
'''Results of the Meeting:''' [[Syntax_checking/Visualisation| Visualisation]]

==M4: May 23th==
*'''Parser Group''': Find out what results you get from the parser
*'''Visualisation Group''': Write a feature that draw the red underline

== May 17th ==
'''Results of Parser Group:''' [[Syntax_checking/Parser| Parser]]

=Team=
Everyone intrested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-ui es-ui@origo.ethz.ch].
At this point, the team is divided into two groups at this point, one responsible for the parser, the other one for visual feedback (like underlininig).

== Visual Feedback ==
* [[User:jabernet| Janick Bernet]] (project leader)
* [[User:fdevries| Fabien de Vries]]
* [[User:indermum| Matthias Indermühle]]
* [[User:clerco| Olivier Clerc]]

== Parser ==
* [[User:maser| Martin Luder]]
* [[User:Chrigu| Christoph Huber]]
* [[User:goalgettah| Ueli Etter]]
* [[User:Squeezie| Michael Schär]]
* [[User:MarkoR| Marko Ristin]]

== Assistant ==
* [[User:classens| Stephan Classen]]

Talk:Syntax checking

2006-05-16T06:17:09Z

Chrigu: /* Meeting 11.5.06 */

Wir sollten irgendwo noch den Namen "SynChé" erwähnen.
engl: we should mentions smowherer the name "SynChé"

'''[[User:FoB|FoB]] 12:52, 20 April 2006 (CEST)'''

'''yes you should!!''' it is your task and duty to fill in more information into this page. you should have a SRS and an introductiory text, and you should also post updates and a TODO list and other interesting stuff here. remember, thsi is not just your project. this is an open source project and everybody can participate. but you only will get help from the comunity if you provide informations on what, why and how you do things.

oh and by the way: '''stick to english'''

== Meeting 11.5.06 ==

Both of the Groups have a Meeting at 4 pm. in the bQm. There we plan our next steps and share informations

'''Group Parser'''
No one of us could compile the Eiffel Studio yet. We will study the code and make a page in this Wiki, in which we describe each class that is useful for our project. And then, we should talking about the interface with the other group.
(Someone of our Group knew, where you can read the Eiffel Studio source code online. Please post the link here. That would be very useful.)

[[User:Indermum|Indermum]] 13:38, 12 May 2006 (CEST) '''Group Visualisation'''

We still have problems to compile Eiffel Studio too. We made a little summary about the classes we need to use under [[Syntax_checking/Visualisation]]

Ah and one other thing. could '''everybody''' pleas insert in his page his e-mail adress and his cell phone number for faster communication and if aviable the msn or icq adress. thx

Talk:Syntax checking

2006-05-16T06:16:41Z

Chrigu: /* Meeting 11.5.06 */

Wir sollten irgendwo noch den Namen "SynChé" erwähnen.
engl: we should mentions smowherer the name "SynChé"

'''[[User:FoB|FoB]] 12:52, 20 April 2006 (CEST)'''

'''yes you should!!''' it is your task and duty to fill in more information into this page. you should have a SRS and an introductiory text, and you should also post updates and a TODO list and other interesting stuff here. remember, thsi is not just your project. this is an open source project and everybody can participate. but you only will get help from the comunity if you provide informations on what, why and how you do things.

oh and by the way: '''stick to english'''

== Meeting 11.5.06 ==

Both of the Groups have a Meeting at 4 pm. in the bQm. There we plan our next steps and share informations

'''Group Parser'''
No one of us could compile the Eiffel Studio yet. We will study the code and make a page in this Wiki, in which we describe each class that is useful for our project. And then, we should talking about the interface with the other group.
(Someone of our Group knew, where you can read the Eiffel Studio source code online. Please post the link here.)

[[User:Indermum|Indermum]] 13:38, 12 May 2006 (CEST) '''Group Visualisation'''

We still have problems to compile Eiffel Studio too. We made a little summary about the classes we need to use under [[Syntax_checking/Visualisation]]

Ah and one other thing. could '''everybody''' pleas insert in his page his e-mail adress and his cell phone number for faster communication and if aviable the msn or icq adress. thx

Talk:Syntax checking

2006-05-15T13:30:03Z

Chrigu: /* Meeting 11.5.06 */

Wir sollten irgendwo noch den Namen "SynChé" erwähnen.
engl: we should mentions smowherer the name "SynChé"

'''[[User:FoB|FoB]] 12:52, 20 April 2006 (CEST)'''

'''yes you should!!''' it is your task and duty to fill in more information into this page. you should have a SRS and an introductiory text, and you should also post updates and a TODO list and other interesting stuff here. remember, thsi is not just your project. this is an open source project and everybody can participate. but you only will get help from the comunity if you provide informations on what, why and how you do things.

oh and by the way: '''stick to english'''

== Meeting 11.5.06 ==

Both of the Groups have a Meeting at 4 pm. in the bQm. There we plan our next steps and share informations

'''Group Parser'''
No one of us could compile the Eiffel Studio yet. We will study the code and make a page in this Wiki, in which we describe each class that is useful for our project. And then, we should talking about the interface with the other group.

[[User:Indermum|Indermum]] 13:38, 12 May 2006 (CEST) '''Group Visualisation'''

We still have problems to compile Eiffel Studio too. We made a little summary about the classes we need to use under [[Syntax_checking/Visualisation]]

Ah and one other thing. could '''everybody''' pleas insert in his page his e-mail adress and his cell phone number for faster communication and if aviable the msn or icq adress. thx

User:Chrigu

2006-05-14T11:02:26Z

Chrigu: /* E-Mail, phone number, Messenger */

== E-Mail, phone number, Messenger ==
chrhuber_at_student.ethz.ch

079/598 83 62

MSN (more in use): huber.c@freesurf.ch

ICQ: 167-439-842

== Work ==
[[Syntax_checking]]

User:Chrigu

2006-05-14T11:02:03Z

Chrigu:

== E-Mail, phone number, Messenger ==
chrhuber_at_student.ethz.ch
079/598 83 62
MSN (more in use): huber.c@freesurf.ch
ICQ: 167-439-842

== Work ==
[[Syntax_checking]]

Talk:Syntax checking

2006-05-11T14:54:32Z

Chrigu:

Talk:Syntax checking

2006-05-11T14:54:07Z

Chrigu: /* Meeting 11.5.06 */

Syntax checking

2006-05-02T18:25:28Z

Chrigu: /* Parser */

[[Category:Projects]]
[[Category:Editor]]

=Overview=
The aim of this project is to provide adequate, but non intrusive feedback to user about syntax errors. This is done by checking syntax as you type and underlining syntax errors by the well knwon wavy red line. Furthermore, error descriptions and possible solutions should be provided.

The Project is named '''SynChé''', which is a combination of syntax and checking.
The ''é'' at the end is important, as a cool name needs either a recursive acronym or a special character from a non English language.

=Software Requirement Specification (SaRS)=
you can find our SaRS [[Syntax_checking/SRS|here]] (comming soon)

=Milestones=

==M1: April 25th==
* Get home-grown EiffelStudio up and running.

==M2: May 2nd==
* '''Put your name in this Wiki!'''
* Analyse source code to certain degree, so discussion about interfaces between parser and visual is possible

==M3: May 9th==
* SRS written
* Overview of relevant classes (BON diagram or more)
* Further Project Milestones specified, based on SRS and knowledge about code

=Team=
Everyone intrested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-ui es-ui@origo.ethz.ch].
At this point, the team is divided into two groups at this point, one responsible for the parser, the other one for visual feedback (like underlininig).

== Visual Feedback ==
* [[User:jabernet| Janick Bernet]] (project leader)
* [[User:fdevries| Fabien de Vries]]
* [[User:indermum| Matthias Indermühle]]
* [[User:clerco| Olivier Clerc]]

== Parser ==
* [[User:maser| Martin Luder]]
* [[User:Chrigu| Christoph Huber]]
* [[User:goalgettah| Ueli Etter]]
* [[User:Squeezie| Michael Schär]]

== Assistant ==
* [[User:classens| Stephan Classen]]

User:Chrigu

2006-05-02T18:24:28Z

Chrigu: /* Work */

== Work ==
[[Syntax_checking]]

User:Chrigu

2006-05-02T18:24:10Z

Chrigu:

== Work ==
[Syntax_checking]

Syntax checking

2006-04-25T13:52:27Z

Chrigu: /* Team */

[[Category:Projects]]
[[Category:Editor]]

=Overview=
The aim of this project is to have a syntax checking done as you type.
Syntax errors should be highlited and eventualy also options for correcting the error should be propossed.

=Milestones=

==M1: April 25th==
* Get home-grown EiffelStudio up and running.

==M2: May ??? ==
* To be completed by the team

=Team=
Everyone intrested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-ui es-ui@origo.ethz.ch]

* [[User:jabernet| Janick Bernet]] (big boss and scapegoat)
* [[User:fdevries| Fabien de Vries]]
* [[User:maser| Martin Luder]]
* [[User:clerco| Olivier Clerc]]
* [[User:indermum| Matthias Indermühle]]
* [[User:chrhuber| Christoph Huber]]
* [[User:classens| Stephan Classen]]

Syntax checking

2006-04-25T13:51:41Z

Chrigu: /* Team */

[[Category:Projects]]
[[Category:Editor]]

=Overview=
The aim of this project is to have a syntax checking done as you type.
Syntax errors should be highlited and eventualy also options for correcting the error should be propossed.

=Milestones=

==M1: April 25th==
* Get home-grown EiffelStudio up and running.

==M2: May ??? ==
* To be completed by the team

=Team=
Everyone intrested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-ui es-ui@origo.ethz.ch]

* [[User:jabernet| Janick Bernet]] (big boss and scapegoat)
* [[User:fdevries| Fabien de Vries]]
* [[User:maser| Martin Luder]]
* [[User:clerco| Olivier Clerc]]
* [[User:indermum| Matthias Indermühle]]
* [[User:classens| Stephan Classen]]
* [[User:chrhuber| Christoph Huber]]