Open deathbeam opened 8 years ago
In pharen is used ^for types So we can write ^Int ^Array:Int
But ^ is also bitwise operator, and in Raxe it is marked as eol operator.
Solved, we are using now <>
classic syntax. But it probably will have some issues, so I am leaving this open.
because > keyword is also used as do-not-insert-semicolon-at-end-of-line keyword. can you change the > keyword to something else?
I am planning to do it, but I still do not know what to use for generics :(
sorry, i'm not familiar with raxe syntax yet. why is there a special marker for end of line? can't \n be enough?
It is not special marker. It is just comparison operator, but raxe check for operators at end of lines for multiline statements.
I think it can be done based on the context. for example, if it starts with ### then the whole text will be scanned until finding ### to close it. Afterwards that text will be parsed.
Right now, in Raxe we have really ugly syntax for generics. We cannot use classic Haxe
<>
syntax for generics:because
>
keyword is also used asdo-not-insert-semicolon-at-end-of-line
keyword.Right now, we have this syntax:
which can be sometimes really ugly and misleading. We need better one, but I do not have any idea on how to make better one.