SRL Archive - FAQ

The semicolon color is blue and is supposed to be red. It compiles fine though. Haven't tested any other instances

From: rj

The semicolon color is blue and is supposed to be red. It compiles fine though. Haven't tested any other instances

Edit:Errm.. I might have a look at it.. Tho don't expect any quick fix.. Haven't been up for doing anything related to Simba latelty

From: rj

The semicolon color is blue and is supposed to be red. It compiles fine though. Haven't tested any other instances

I dont think it's limited to the semi-colon. Starting a new line, resets the coloring, but Simba still reads it as part of the '…'

begin
  writeLn('asdasdasd
  hey!!!');
end;

this will output both lines of text, even tho the color would indicate that hey!!! isn't included in the '…' interval. The new line resets the coloring, but Simba still reads it fine.

EDIT 1 : wait lol on the forums it appears correctly! but in Simba it doesn't!

EDIT 2:[ATTACH=CONFIG]25426[/ATTACH]

From: fady
this will output both lines of text

What? It doesn't compile :S..

From: slacky
Edit:Errm.. I might have a look at it.. Tho don't expect any quick fix.. Haven't been up for doing anything related to Simba latelty

Don't bother? Not a bug afaict.. "Error: EOL while scanning string literal at line 3".

begin
  writeLn('asdasdasd
  hey!!!');
end;

On the "writeLn" line, the string isn't terminated. The code is invalid because OP didn't continue the line with the concatenation/line break continuation operator "+".


@OP:

begin
  writeLn('asdasdasd' + //There's a reason DTM's have a + sign at the end such that the literal continues on the next line.
  'hey!!!');
end;

From: Brandon
What? It doesn't compile :S..




Don't bother? Not a bug afaict.. "Error: EOL while scanning string literal at line 3".

begin
  writeLn('asdasdasd
  hey!!!');
end;

On the "writeLn" line, the string isn't terminated. The code is invalid because OP didn't continue the line with the concatenation/line break continuation operator "+".


@OP:

begin
  writeLn('asdasdasd' + //There's a reason DTM's have a + sign at the end such that the literal continues on the next line.
  'hey!!!');
end;

const
  code = 'ggfg
  g';

begin
  writeln(code);
end.

Compiles fine for me, the only difference is that it outputs it into 2 lines

From: rj

const
  code = 'ggfg
  g';

begin
  writeln(code);
end.

Compiles fine for me, the only difference is that it outputs it into 2 lines

I think @slacky introduced a bug, that should only work when multiline string using " rather than '.

From: rj
Compiles fine for me, the only difference is that it outputs it into 2 lines

The code is in fact, invalid. It doesn't compile for me (and shouldn't compile):

From: Brandon
The code is in fact, invalid. It doesn't compile for me (and shouldn't compile): -snip-

Weird behaviour.. compiles for me as well

Compiled successfully in 203 ms.
ggfg
  g
Successfully executed.

What version of Simba are you using? rev 1100 here

From: Brandon
The code is in fact, invalid. It doesn't compile for me (and shouldn't compile):

Your simba is different, I'm assuming you are using the newest one that hasn't been added to the updater

From: Brandon
The code is in fact, invalid. It doesn't compile for me (and shouldn't compile):

I was expecting it not to work too but it does!




I have Simba rev 1100

From: Brandon
What? It doesn't compile :S..
Don't bother? Not a bug afaict.. "Error: EOL while scanning string literal at line 3".

begin
  writeLn('asdasdasd
  hey!!!');
end;

rj is using the Simba Stable, it doesn't contain the latest Lape yet, so he don't get that EOL error.
I changed string-parsing in the latest lape. To do multiline-strings you are forced to do as you say ('asd'+<newline>'123') OR by using double-quotes.

It's indeed not really a bug considering strings are only supposed to span over one line. The lape version you have has corrected string handling.

"Issue" will be solved as soon as the updated Lape is in Simba Stable.