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

Consider case, when object is encapsulated in ".if" and it works like 'other object' and wraps by new ".if". #5

Open
MikhailLipanin opened this issue Jul 26, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@MikhailLipanin
Copy link
Member

No description provided.

@MikhailLipanin MikhailLipanin added the enhancement New feature or request label Jul 27, 2022
@MikhailLipanin
Copy link
Member Author

for example, if there are several ".forward"/"backward" inside goto, then for "other" objects, that should be encapsulated in additional ".if" objects with "flag-check", this will be respresented as:

if.
  eq.
    flag1
    x
  seq
    if.
      eq.
        k
        seq
          flag2.write 0
        z
      TRUE
  if.
    eq.
      flag2
      1
    seq
      TRUE
    TRUE

but not like that:

if.
  eq.
    flag1
    x
  seq
    if.
      eq.
        k
        seq
          flag2.write 0
        z
      TRUE
  TRUE

So, need to consider cases with branching and ".if" object.

@0pdd
Copy link

0pdd commented Dec 23, 2022

@MikhailLipanin the puzzle #109 is still not solved.

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

No branches or pull requests

2 participants