Jump to: navigation, search

Difference between revisions of "ETrice/GSoC/2012/GACL"

(TypeDeclaration)
Line 26: Line 26:
  
 
==== TypeDeclaration  ====
 
==== TypeDeclaration  ====
Syntax to be used is :-
+
 
 +
Syntax to be used is :-  
  
 
   type prt type xyz int
 
   type prt type xyz int
  type pqr { int Hello , char ch , prt p , op f1:int() , op f2:char(char,char) }    type pqr' {pqr e1}
+
type pqr { int Hello , char ch , prt p , op f1:int() , op f2:char(char,char) }    type pqr' {pqr e1}
  prt {pqr p};
+
prt {pqr p};
  
What the above code is intended to do is as following :-
+
What the above code is intended to do is as following :-  
  
*Declares a type prt ended with whitespace
+
*Declares a type prt ended with whitespace  
*Creates a type xyz same as int where type declaration ended with newline
+
*Creates a type xyz same as int where type declaration ended with newline  
*Creates a type pqr representing a structure rather class with abstracted elements Hello of type int , ch of char , p of type prt and f1 and f2 of type op i.e. Operations . f1 and f2 can take use of their arguments and also other elements of pqr i.e. Hello and ch in this case and ended with a tab .
+
*Creates a type pqr representing a structure rather class with abstracted elements Hello of type int , ch of char , p of type prt and f1 and f2 of type op i.e. Operations . f1 and f2 can take use of their arguments and also other elements of pqr i.e. Hello and ch in this case and ended with a tab .  
*Creates a type pqr' with e1 of pqr abstracted in it ended with newline
+
*Creates a type pqr' with e1 of pqr abstracted in it ended with newline  
 
*Creates prt declared already with p of type pqr abstracted in it ended with semicolon
 
*Creates prt declared already with p of type pqr abstracted in it ended with semicolon
  
Grammar to be used is :-
+
Grammar to be used is :-  
  
 
   { "type" typename [ existingtype | "{" TypeCode "}" ] [";" | "\n" | "\t" | " "] } | {typename typecode}
 
   { "type" typename [ existingtype | "{" TypeCode "}" ] [";" | "\n" | "\t" | " "] } | {typename typecode}

Revision as of 12:50, 31 March 2012

Generic Action Code Language (GACL)

GACL is the language to describe the Detail Code for execution of ROOM Models in eTrice plugin . GACL aims at dealing with all features commonly available in imperative languages , especially Java , C/C++ . It will act as complement of current version of eTrice which uses code written in target language stored in a string as execution code . GACL would make user able to write execution code independent of target language .

Development Details and Core Information

Features of GACL

  • Variable Declarations ( with optional initializers ) and Function Declaration .
  • Comparison & arithmetic expressions .
  • Basic types , and user defined types .
  • If-else blocks and ladders .
  • For , while , for each , enhanched for each .
  • Support for iterators (that can be used by for each loops ) .
  • Function Calls with arguments & diff types i.e. ref/value/address .
  • type checking and as much as possible implicit type casting .
  • Casts corresponding to static casts in C .

Thoughts on Syntax

Although syntax for GACL is still being designed but here are few thought regarding syntax .

Empty

 {}

TypeDeclaration

Syntax to be used is :-

 type prt type xyz int
type pqr { int Hello , char ch , prt p , op f1:int() , op f2:char(char,char) }    type pqr' {pqr e1}
prt {pqr p};

What the above code is intended to do is as following :-

  • Declares a type prt ended with whitespace
  • Creates a type xyz same as int where type declaration ended with newline
  • Creates a type pqr representing a structure rather class with abstracted elements Hello of type int , ch of char , p of type prt and f1 and f2 of type op i.e. Operations . f1 and f2 can take use of their arguments and also other elements of pqr i.e. Hello and ch in this case and ended with a tab .
  • Creates a type pqr' with e1 of pqr abstracted in it ended with newline
  • Creates prt declared already with p of type pqr abstracted in it ended with semicolon

Grammar to be used is :-

 { "type" typename [ existingtype | "{" TypeCode "}" ] [";" | "\n" | "\t" | " "] } | {typename typecode}

VariableDeclaration

 [ type ] varname [ "=" { varname2 | Expression } ] { ";" | "\n" }

Expression

 { ArithmeticExpression | LogicalExpression }
ArithmeticExpression
 { Expression { "+" | "-" | "*" | "/" | "**" | "^" | "%" | "div" } Expression } 
| {Expression { "++" | "--" } } | { { "++" | "--" } Expression }
LogicalExpression
 { Expression { "<" | "<=" | "==" | ">" | ">=" | "|" | "||" | "&" | "&&" | "^" } Expression }

Statement

 { Expression | Expression }

StatementList

 { Empty | Statement Statementlist }

Program

 {  Statementlist }


Disambiguation

The syntax used to specify the grammar in brief is

  • Things written in double quotes ("") stand as string written in source .
  • Content inside braces ({}) represents required content .
  • Content inside square brackets ([]) represents optional content .
  • Everything rest is either terminal or non-terminals .
  • Empty and statement list need a more thought to be done . We would surely finally come up with a better solution .

Project Proposal

Click Here to see the project proposal at gsoc's website .

Click Here to see the project proposal in my github repository .

Useful Links