Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[docs] SDL format needs to be described #32

Open
thedeemon opened this issue Sep 22, 2015 · 6 comments
Open

[docs] SDL format needs to be described #32

thedeemon opened this issue Sep 22, 2015 · 6 comments
Labels

Comments

@thedeemon
Copy link

Neither official SDL site nor its mirror are working anymore, so SDL format itself is a mystery now.

@marler8997
Copy link

SDL was already a mystery:)

@Abscissa
Copy link
Collaborator

I've now mirrored the site here (luckily grabbed from when web.archive.org was still serving a mirror):
http://semitwist.com/sdl-mirror/Home.html

The main language description is on this page:
http://semitwist.com/sdl-mirror/Language+Guide.html

I'm leaving this ticket open because SDLang-D should still provide a documented spec on it's own.

@Abscissa
Copy link
Collaborator

Abscissa commented Feb 7, 2016

There's also now a description here: http://sdlang.org/

But again, a more formal spec is still needed.

@trikko
Copy link

trikko commented Jun 8, 2016

Aren't parentesys on blank line accepted? Why? I put them wrong every single time.

@Abscissa
Copy link
Collaborator

Abscissa commented Jun 8, 2016

On 06/08/2016 11:58 AM, Andrea Fontana wrote:

Aren't parentesys on blank line accepted? Why? I put them wrong every single time.

Despite what the use of curly braces may suggest, SDLang is a
newline-terminated language, not a semicolon-terminated one. So the
newline ends the tag. Additionally SDLang supports anonymous tags, with
no name. Therefore, this:

foo
{
bar
}

Is two tags:

  1. "foo" tag with no children.
  2. An unnamed anonymous tag with one child, "bar".

As with most newline-terminated languages, there IS a line-continuation
operator:

foo
{
bar
}

That makes the parser ignore the newline and treat it as:

foo {
bar
}

@Abscissa
Copy link
Collaborator

Abscissa commented Jun 8, 2016

Come to think of it, that's something that would be important to include in an SDLang FAQ or something (note to self).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants