-
Notifications
You must be signed in to change notification settings - Fork 126
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
Why <metas>
attribute in XMIR is optional?
#1522
Comments
@yegor256 WDYT? |
@MikhailLipanin I didn't understand the problem. What doesn't work now? |
When I have this program:
I get the following XMIR: (Note that here there is no
But when I have this program (the only difference in
I get the following XMIR:
Note, that the difference here is in I think it is because some XSL - templates depends on So, we can make @yegor256 FYI |
@MikhailLipanin why it's a problem? Yes, this is how |
@yegor256 Because we don't correctly add |
So in first example, I can't say, what is |
@MikhailLipanin try to always report a bug in this format: 1) I do this, 2) I expect this result, 3) I'm getting this instead. |
Here, I expected in both examples of EO-programs the second XMIR, but get it only in second example |
@pollyvolk please assist |
@pollyvolk @MikhailLipanin @yegor256 I believe |
@mximp I don't mind, let's make it mandatory |
Just to make it clear: it will not be mandatory from EO language point of view but rather |
This one is related to #1323 |
@mximp let's make it mandatory in XMIR (let's update |
I have this program:
Since
<metas>
is optional attribute in XMIR now, and in the program above there is noalias
-es andprobe
-s (and others), there is no<metas/>
section in final XMIR.But work of
add-probes.xsl
depends on<metas>
section and without it, XSL will not work.So, if I add simple
meta
---package
, it will work:So, we can make
<metas>
section is mandatory in XMIR-s or rewriteadd-probe.xsl
and all others XSL-s (if they are exist).The text was updated successfully, but these errors were encountered: