jamice / yajco Goto Github PK

1. aktualne nedokaze spravne spajat koncepty z anotacneho procesora a tie ktore 
uz su nacitane z JAR, nakolko v TypeElement v JAR uz neobsahuju anotacie YAJCo

Je potrebne spravit samostatne spracovanie konceptov z aktualnych zdrojovych 
kodov a z JAR ale tak aby sa dokazal pri kazdom pozadovanom koncepte znova 
rozhodnut, ze ake spracovanie sa ma pouzit

What steps will reproduce the problem?
1. use long in class constructors 
2. cannot find proper constructor - expects int (yajco knows only int internaly)

spravit upravu na hladanie konstruktorov nezavazne, ci je tam parameter int 
alebo long

What steps will reproduce the problem?
1.When you create concept with name 'object' or 'interface' generated code is 
wrong.

What steps will reproduce the problem?
1.create class Name<T> 
2.create subclass e.g.: SubName<String>
3.generate language

What is the expected output? What do you see instead?
Generator doesnt go through all subtypes in case of class with generics

1. YAJCo language model uses concepts name which are in collision with YAJCO 
language
2. e.g.: tokens, concept ... see attached file - it is not possible to parse it 
into YAJCo
3. problems during generation of parser, if we use "enum" as variable name, it 
is actually keyword in Java = generated parser is not compilable

What is the expected output? What do you see instead?
Bolo by vhodne zistovat, ci sa niekde nepouzivaju klucove slova a tieto 
nahradit pripadne pripojit k nim _podciarkovnik na zaciatok.

1. ak v jednom jazyku mame korenovy koncept sk.tuke.Program
2. nemozeme nasledne pouzit balik sk.rovina.Priamka
3. tento pristup je problematicky hlavne pre kompoziciu