SCOOP-A3: Compiler adaptation - Revision history

Alexander Kogtenkov: /* Decisions */ Added notes on CECIL and storable

2010-08-25T15:18:14Z

‎Decisions: Added notes on CECIL and storable

Alexander Kogtenkov: /* Open questions */ Cosmetics

2010-08-25T11:21:45Z

‎Open questions: Cosmetics

Alexander Kogtenkov: Introduced several new sections with more details

2010-08-25T11:21:10Z

Introduced several new sections with more details

Alexander Kogtenkov: Added a note that processor syntax will not be supported in 6.7

2010-08-19T13:09:45Z

Added a note that processor syntax will not be supported in 6.7

Alexander Kogtenkov: Added some details

2010-06-05T10:58:28Z

Added some details

Alexander Kogtenkov: Turned user names into links

2010-05-25T09:40:09Z

Turned user names into links

Alexander Kogtenkov: Added a new category: compiler

2010-05-25T09:35:44Z

Added a new category: compiler

Ted: New page: {{UnderConstruction}} Category:Concurrency_(SCOOP) Team: Alexander, Ted * Parsing is already taken care of * Code generation closely connected with work on the scheduler (A1, A2) * Va...

2010-05-25T09:31:11Z

New page: {{UnderConstruction}} Category:Concurrency_(SCOOP) Team: Alexander, Ted * Parsing is already taken care of * Code generation closely connected with work on the scheduler (A1, A2) * Va...

New page

{{UnderConstruction}}
[[Category:Concurrency_(SCOOP)]]
Team: Alexander, Ted

* Parsing is already taken care of
* Code generation closely connected with work on the scheduler (A1, A2)
* Validity rules are important; part of the challenge is to turn the SCOOP type system
(devised by Piotr Nienaltowski) into compiler verifications and meaningful error messages.

@@ Line 25: / Line 25: @@
 #* Separate and non-separate class types are generated separately, i.e. <e>ANY</e> and <e>separate ANY</e> get different code.
 #* Generic derivations with separate and non-separate generics are generated separately, i.e. <e>ARRAY [G]</e> and <e>ARRAY [separate G]</e> get different code.
 = Open questions =
 * Shall separate types be supported in CECIL? If yes, how is this done?

@@ Line 26: / Line 26: @@
 #* Generic derivations with separate and non-separate generics are generated separately, i.e. <e>ARRAY [G]</e> and <e>ARRAY [separate G]</e> get different code.
 = Open questions =
-* Shall separate types be supported in CECIL? If yes, how this is done?
+* Shall separate types be supported in CECIL? If yes, how is this done?
 = Progress =
 {| border="1" style="border-collapse: collapse; border-width: 1px; border-style: solid;"

@@ Line 3: / Line 3: @@
 [[Category:Compiler]]
 Team: [[User:Alexander Kogtenkov|Alexander Kogtenkov]], [[User:Ted|Ted]]
+= Summary =
 * '''Parser'''
 ** Support only separate type declarations (exclude separate class declarations).
@@ Line 15: / Line 15: @@
 ** C code
 ** CIL code

@@ Line 6: / Line 6: @@
 * '''Parser'''
 ** Support only separate type declarations (exclude separate class declarations).
-** Provide syntax to refer to the processors.
+** Provide syntax to refer to the processors (not supported in [[EiffelStudio_6.7_Releases|6.7]]).
 ** Take into account the possibility to use anchors.
 * '''Type checking''' introduces new

@@ Line 4: / Line 4: @@
 Team: [[User:Alexander Kogtenkov|Alexander Kogtenkov]], [[User:Ted|Ted]]
-* Parsing is already taken care of
+* '''Parser'''
-* Code generation closely connected with work on the scheduler (A1, A2)
+** Support only separate type declarations (exclude separate class declarations).
-* Validity rules are important; part of the challenge is to turn the SCOOP type system
+** Provide syntax to refer to the processors.
-  (devised by Piotr Nienaltowski) into compiler verifications and meaningful error messages.
+** Take into account the possibility to use anchors.

@@ Line 1: / Line 1: @@
 {{UnderConstruction}}
 [[Category:Concurrency_(SCOOP)]]
 Team: Alexander, Ted