#531 closed defect (invalid)
psMetadataConfigFormat() does not properly handle nested psMetadata
| Reported by: | jhoblitt | Owned by: | |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | types | Version: | 0.7.0 |
| Severity: | normal | Keywords: | |
| Cc: |
Description
The attached example outputs this format. Which is obviously wrong.
bar METADATA
bar METADATA
foo S32 1 #
END #
END #
Attachments (1)
Change History (5)
by , 21 years ago
| Attachment: | nestedmd.c added |
|---|
comment:1 by , 21 years ago
| Owner: | changed from to |
|---|---|
| Summary: | psMetadataConfigFormat() does not properly handle nested psMetadata → psMetadataConfigFormat() does not properly handle nested psMetadata |
comment:2 by , 21 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Actually, I think that output is correct. If you notice in your code, you
print the output of md3. I changed this to md4 and got the following,
boing METADATA
baz METADATA
bar METADATA
foo S32 1 #
END #
END #
END #
I assume this is closer to what you would expect?
I will take a look at the unnecessary printing of #'s.
Note:
See TracTickets
for help on using tickets.

formatting nested metadata