Oberon-07

[0CodErr]

Hello!
At first thanx for the best text editor.

I tried to implement Oberon07 syntax scheme.
Oberon07 report can be found here:
inf.ethz.ch/personal/wirth/Oberon/Oberon07.Report.pdf
See topics on the KolibriOS forum in russian:
board.kolibrios.org/viewtopic.php?f=33&t=2443&start=45#p70428
board.kolibrios.org/viewtopic.php?f=33&t=2443&start=60#p70436
and last update:
board.kolibrios.org/viewtopic.php?f=33&t=2443&start=60#p70495

I have a problem with an implementing nested comments.
Current implementation — is not completely right way.

[alex]

Hi,

thanks for sharing.

Can you please provide an example file in Oberon language for testing the schema?
Also, please, based on the example explain what works not as expected.
I will try to help.

BR, Alex.

[0CodErr]

explain what works not as expected

Problem is that comments can only be nested twice(but no more), i.e.:

Code () Select Expand


(*
   (*
    *
    *  (* *** *)
    *
    *)
*)That's because I don't know how to do it right way.
I implemented it like this:

Code (xml) Select Expand

<Style id="comment"...
  <Blocks>
    <Block open="//" close="\n"/>
    <Block open="(*" close="*)"/>
  </Blocks>
</Style>
<Style id="comment1"...
  <Containers>
    <Open id="comment"/>
    <Close id="comment"/>
  </Containers>
  <Blocks>
    <Block open="(*" close="*)"/>
  </Blocks>
</Style>
<Style id="comment2"...
  <Containers>
    <Open id="comment1"/>
    <Close id="comment1"/>
  </Containers>
  <Blocks>
    <Block open="(*" close="*)"/>
  </Blocks>

Can you please provide an example file in Oberon language for testing the schema?

I provided two examples in the attachment.

[alex]

Hi,

for allowing comments nesting, you only need to allow that comment style is also allowed in normal style. Any style is implicitly allowed inside of normal style until you do not overwrite a container section. Than only defined there (or inherited explicitly defined containers) are allowed.

Code (xml) Select Expand

<Style id="comment" name="Comments" text="1" bold="0" italic="1" underline="0" clr="Comments">
<Containers>
<Open id="normal"/>
<Open id="comment"/>
</Containers>
<Blocks>
<Block open="//" close="\n"/>
<Block open="(*" close="*)"/>
</Blocks>
</Style>

I agree, that it is not obvious and also was not documented. So, I have updated the wiki accordingly:
https://wiki.hippoedit.com/syntax/containers

I have updated your schema (comments + some other small adjustments) and placed it, together with examples on guthub, so that we can track changes easily:
https://github.com/hippoedit/syntax/tree/master/Oberon-07

The schema already looks OK and if you do not mind, I can place it in the online repository, that users can download the schema automatically when opening Oberon files.
Is it OK for you?

If you have other questions, I would be glad to help.

BR, Alex.
P.S: and thank you for writing in English

[alex]

• to not force closing element on scopes, one can set strict=false. Wiki...
• Regular expressions are supported. But not in SPECIFICATION section, only in Styles. You can create an extension for numbers style, and add there needed Regexp. But there are some limitations for regular expressions.

Code (xml) Select Expand


<Style id="number" extend="true">
  <Blocks>
    <Block open="0x">
       <Close noneof="0-9A-Fa-fU"/>
    </Block>
    <Regexp text="\\d+e[\\-\\+]\\d+"/>
    <Regexp text="\\d+(?:[ulUL]{1,2}|f)"/>         
  </Blocks>
</Style>

[0CodErr]

for allowing comments nesting, you only need to allow that comment style is also allowed in normal style.

Oh, thanx! I didn't know about it.

I have updated your schema (comments + some other small adjustments) and placed it, together with examples on guthub, so that we can track changes easily

Thanx again 

The schema already looks OK and if you do not mind, I can place it in the online repository, that users can download the schema automatically when opening Oberon files.
Is it OK for you?

Yes, it OK for me.

[alex]

Ok, then I would add it to the repository.

Please check also my advises about strict and regular expressions.
You may submit your changes directly to GitHub. Send me your github registration name and I would add you as a collaborator.

New syntax scheme appreciated by a HippoEDIT license if you need it - I have sent you a personal message with details.

[alex]

Published: https://hippoedit.com/Oberon07-editor/