mirror of
https://github.com/ton-blockchain/ton
synced 2025-02-15 04:32:21 +00:00
30572c77d6
They work alongside Lisp-style ;; and {--}, without any #pragma.
Conceptually, a new syntax should be disabled by default
and activated using a special compiler option.
But now, we don't have an easy way to provide compiler options
in func-js, blueprint, etc.
Note, that introducing per-file #pragma is a wrong approach here,
since if we want to fire human-readable error on using '//' without pragma,
lexer should nevertheless work differently.
(this could be controlled by a launch option, but see above)
11 lines
114 B
Text
11 lines
114 B
Text
int main() {
|
|
return 0;
|
|
}
|
|
|
|
{-
|
|
int ...
|
|
|
|
/*
|
|
@compilation_should_fail
|
|
@stderr comment extends past end of file
|
|
*/
|