Moritz Activity
transfer xml into specific text-formats (html, dot, source-code, ...)
Brought to you by:
eckard_klotz
Activity for Moritz
-
Eckard Klotz posted a comment on discussion Help
Hello Cheetos Su. Please accept my apologize for my late reply. Unfortunately the filename mentioned in the description is outdated and you will not find it any more. How ever you will find in the root directory several shell-scripts (on Linux) or batch-files (on Windows). Moritz is able to parse sources of different programming languages today and thus you will find different example sources and different scripts. Those which contain Moritz in the name will start the complete process for creating...
-
Cheetos Su posted a comment on discussion Help
Hi All, I try to use Moritz. In https://sourceforge.net/projects/moritz/files/Moritz_2.x/DevelopmentFor_2_1_0/Snapshot_2_0_2/, it says: First Steps Start the bat/sh-file named MxMrtz. It should a start demo-run of abc2xml and xml2abc. If this process ends successfully you can find an xml-output of abc2xml in the folder xm and the html-output of Moritz in the folder nsd. But I cannot find file named MxMrtz. How to find this file? Thanks!
-
Hello Hariharan Mari. Sorry but I'm not satisfied by your modification. You have not provided source examples which demonstrate your issue and which could be added to the "UserExample.c" source for testing purpose in the future when other changes will be implemented. It seams to be based on the latest release grammar but not on the latest patch . Thus we would lose all bug-fixes done since the release. Your syntax rule is using string - constants which seem to be very user specific. This is not a...
-
Hello Hariharan Mari. Sorry but I'm not satisfied by your modification. You have not provided source examples which demonstrate your issue and which could be added to the "UserExample.c" source for testing purpose in the future when other changes will be implemented. It seams to be based on the latest release grammar but not on the latest patch . Thus we would lose all bug-fixes done since the release. Your syntax rule is using string - constants which seem to be very user specific. This is not a...
-
Hariharan Mari posted a comment on discussion Development
Previously the Moritz tool could not parse when we have user specific attribute in the declaration eg. static int array[10] USER_ATTRIBUTE; (Here USER_ATTRIBUTE is a Macro) will now be able to parse. Similary in code MACRO(const int variable = 0); type_qualifier and type specifier before cast expression in the assignment_expression is not parsed before and now it can be parsed. Please let me know if this change can be accepted for the tool or if you suggest a better way to parse the c code for me....
-
Hello Hariharan Mari. To be honest I don't understand your comment. Previously the Moritz tool could not parse ... ... and now it can be parsed. Do you have now an issue or not? Your description suggests that you break the syntax-rules in the source by using preprocessor defines. Since the parser has no own preprocessor, it tries to analyse the source as it is. The reason for this is the fact that Moritz should document the source and not the resulting binary. This may result in a parser-termination...
-
Previously the Moritz tool could not parse when we have user specific attribute in the declaration eg. static int array[10] USER_ATTRIBUTE; (Here USER_ATTRIBUTE is a Macro) will now be able to parse. Similary in code MACRO(const int variable = 0); is not parsed before and now it can be parsed.
-
Previously the Moritz tool could not parse when we have user specific attribute in the declaration eg. static int array[10] USER_ATTRIBUTE; (Here USER_ATTRIBUTE is a Macro) will now be able to parse. Similary in code MACRO(const int variable = 0); is not parsed before and now it can be parsed.
-
Hello Mr. Jalabert. As far as I understand the topic you face more than the "..." issue. Is this correct? Please provide me examples of your issues and I will take a look in the next days. Best regards, Eckard Klotz.
-
Philippe Jalabert posted a comment on discussion Development
Hello, could you please tell me how I could add to the grammar files the recognition of "..." ?
-
Hello Mr. Dourval . Please accept my apologize for my late reply. But my real-life tasks challenged me in the last days. To be honest I still don't exactly your issue. But I think you are currently struggling with adding the text-snippets to the doxygen output. Thus I hope that the attached Tutorials will help you. It would be nice if you have a look and if you still have some doubts please describe your issue based on the examples provided with the Tutorials. Best regards, Eckard Klotz.
-
Clement Dourval posted a comment on discussion Help
Hi, I'm new in moritz and I'm not finding how to change what I want. Basically, I'm managing to generate everything correctly and use it with @dotfile and @copydoc tags But I'd like to just generate everything, and add it automatically added to the final doxygen documentation regardless of user documenting the code. just to be clear this is an example of txt doxygen documentation file generated : /*! @file byte_utils_c_F_FillIn16.txt <H1> byte utils c F FillIn16 </H1> @dotfile byte_utils_c_F_FillIn16.dt...
-
xml2abc concats paths to create logfiles -- fails with absolut paths
-
struct initializer with condition
-
brackets confusing the parser
-
int16_t not supported (but uint16_t is)
-
Moritz_Win_2020_06_10, XML parsing based on directory is not working
-
Hello Lubos Hubka . Thanks for this short completion of the story. I will close this topic now. In the case that you face other issues could you pleas open an own topic for each issue in the discussion forum first. We could than still decide afterwards if it is a bug or more a help-topic. But it will easier for other newbies to find an to read the topic if they face a similar issue. Stay well and healthy. Best regards, Eckard Klotz.
-
Lubos Hubka posted a comment on ticket #22
So, this did the trick: <Common name="Common" keepValideCode="Implicit"/>
-
Hallo! Sorry for the delay, it's holiday time. So the problem was quite trivial: Mine wrong config: <Source> <FolderName value="./src/" root="SourcePath" fileAttachment=".c" recursive="Yes" doNotSkip="Yes"/> </Source> Yours working config <Source> <FolderName value="./src/" root="SourcePath" fileAttachment=".c" recursive="Yes" doNotSkip="Yes"> <Common name="Common" keepValideCode="Implicit"/> </FolderName> </Source>
-
Hello Lubos Hubka . That's good to read. Could you give us a short description of your finding so that other users may learn from it? Even the closing of this topic will move it from the list of active bugs to the list of closed ones interested users may still open it by entering the sub list of closed tickets. Stay well and healthy. Best regards, Eckard Klotz.
-
Hallo Mr. Klotz! I have got it! Pls. feel free to close this problem report. Many thanks. Best regards. Lubos
-
Hello Lubos Hubka . Could you provide your "not_working_ansi_c_abc2xml_cfg.xml" file? Then I should be able to see what's wrong. Please find attached If this is still not helping you please read again the last part of my post before. I mean "How ever let's do it step by step. ..." In the case that you get no output it may be helpful for me if you would provide the log text-files. Stay well and healthy. Best regards, Eckard Klotz.
-
Hallo Mr Klotz. Well, then I'm making something terribly wrong. I have replaced mine binaries with last patched (bin_Windows_64bit_32bit.zip from 2020-12-23). But I still have no result. I think I have problem with abc2xml, because when I run not_working_ansi_c_create.bat and then working_ansi_c_create.bat, I get 2 completely different xml files - the content is different. Could you provide your "not_working_ansi_c_abc2xml_cfg.xml" file? Then I should be able to see what's wrong. Thanks. Best regards....
-
Hallo Mr Klotz. Well, then I'm making something terribly wrong. I have replaced mine binaries with last patched (bin_Windows_64bit_32bit.zip from 2020-12-23). But I still have no result. Could you provide your "not_working_ansi_c_abc2xml_cfg.xml" file? Then I should be able to see what's wrong. Thanks. Best regards. Lubos
-
Hello Lubos Hubka . Sorry for delay, during weekend I'm usually not working with the computer. No issue week end is week end. And I'm sorry but I'm not sure I understood your answer. The NSD is not generated even when I omit the <Common name="Common" and keepValideCode="Implicit" from the config file. I hope that the modification you have done before your second response has clarified this point for you. The reason why you have to place the "Common" configuration in a sub-node is that this is potentially...
-
Hallo Mr. Klotz. Sorry for delay, during weekend I'm usually not working with the computer. And I'm sorry but I'm not sure I understood your answer. The NSD is not generated even when I omit the <Common name="Common" and keepValideCode="Implicit" from the config file. So now it looks like: <Source> <!-- to use all c-files in the folder and its sub-folders --> <!-- FolderName value="./src/" root="SourcePath" fileAttachment=".c" recursive="Yes" doNotSkip="No"/ --> <FolderName value="./src/" root="SourcePath"...
-
OK, I have also tried the config you proposed: <Source> <!-- to use all c-files in the folder and its sub-folders --> <!-- FolderName value="./src/" root="SourcePath" fileAttachment=".c" recursive="Yes" doNotSkip="No"/ --> <FolderName value="./src/" root="SourcePath" fileAttachment=".c" recursive="No" doNotSkip="Yes" > <Common name="Common" keepValideCode="Implicit"/> </FolderName> </Source> But the result is even worse - in previous run there was an empty HTML file generated. Now there is nothing....
-
OK, I have also tried the config you proposed: <foldername value="./src/" <br=""> root="SourcePath" fileAttachment=".c" recursive="No" doNotSkip="Yes" ></foldername> <Common name="Common" keepValideCode="Implicit"/> But the result is even worse - in previous run there was an empty HTML file generated. Now there is nothing. Have you tried the configuration? Did it worked for you? Because if yes, that means I have different version of moritz binaries than you.
-
Hallo Mr. Klotz. Sorry for delay, during weekend I'm usually not working with the computer. And I'm sorry but I'm not sure I understood your answer. The NSD is not generated even when I omit the <Common name="Common" and keepValideCode="Implicit" from the config file. So now it looks like: <foldername value="./src/" root="SourcePath" fileattachment=".c" recursive="No" donotskip="Yes"> </foldername> But nothing has changed. I will go again through the tutorials, but so far I see no solution. Thank...
-
Moritz_Win_2020_06_10, XML parsing based on directory is not working
-
Hello Lubos Hubka . Please confirm that your issue is solved with my proposal. If you like to discuss some details around pleas open a new topic in the discussion forum since this bug topic will be not easily visible any more once i close it. Best regards, Eckard Klotz.
-
Hello Lubos Hubka . The reason of your issue is not a bug but a wrong configuration. This is the folder configuration in your not working example: <Source> <!-- to use all c-files in the folder and its sub-folders --> <!-- FolderName value="./src/" root="SourcePath" fileAttachment=".c" recursive="Yes" doNotSkip="No"/ --> <FolderName value="./src/" root="SourcePath" fileAttachment=".c" recursive="No" doNotSkip="Yes" Common="Common" keepValideCode="Implicit" /> </Source> You have extended the list...
-
kein problem.
-
Hello Lubos Hubka . Thanks for your zip-file. I will take a look to it but may be not before weekend. Stay negative also by keeping a positive mindset. Best regards, Eckard Klotz.
-
Hallo Mr. Klotz! Thanks for the fast response. I'm sending my test environment. working_ansi_c_create.bat - good case not_working_ansi_c_create.bat - bad case1 Stay negative! ;) Best regards. Lubos
-
Hello Lubos Hubka . First of all the XML output of Doxygen is only used to add links to the Doxygen documentation if needed. But Moritz is not able to generate diagrams from it, since the structure is differing in detail. * Thus your case 2 is a normal case and no bug. For your case 1 please provide an example that contains complete file "ansi_c_abc2xml_cfg.xml" as well as an example source to reproduce your issue. * It may be helpful if you provide your good case also. Thanks for your understanding....
-
Moritz_Win_2020_06_10, XML parsing based on directory is not working
-
Hello Wasili. sorry for the late reply. I'm quite bussy this days. No issue my vacation is over as well and my main focus is set on my profession also. I can't provide the the log and xml files you requested, as they contain confidential code. I will try to get an compiler installed on my machine to build the Moritz binaries and check where xml2abc is crashing. I can understand that you don't want to provide files related to your work. But even you could locate the exact code-line where the application...
-
Hello Wasili. sorry for the late reply. I'm quite bussy this days. No issue my vacation is over as well and my main focus is set on my profession also. I can't provide the the log and xml files you requested, as they contain confidential code. I will try to get an compiler installed on my machine to build the Moritz binaries and check where xml2abc is crashing. I can understand that you don't want to provide files related to your work. But even you could locate the exact code-line where the application...
-
Wasilios Goutas posted a comment on discussion Help
Hi Eckard, sorry for the late reply. I'm quite bussy this days. I can't provide the the log and xml files you requested, as they contain confidential code. I will try to get an compiler installed on my machine to build the Moritz binaries and check where xml2abc is crashing. Best regards Wasili
-
Hello Wasili. I hope you are not completely disappointed by the issues you are currently face. It's not that I want to tell you that the root-cause is just located on the user side. But without some more input from your side I'm not able to reproduce and to solve your problem. Thus please allow me to ask again for the following files: Batch-file you use to call the binaries [MoritzProject]\ ansi_c_create.bat Configuration file you use wile calling binaries [MoritzProject]\ cfg\ ansi_c_abc2xml_cfg.xml...
-
Hello Wasili. Similar to what I have mentioned in your topic latest patched binaries and SVN dump of 23rd Dec 20 -- combination not working I will not be able to evaluate your issue without knowing the batch-file you use to call the binaries and the configuration file you use wile calling xml2abc. The XML files mentioned above may be helpful also. In addition please provide the complete log-output of all binaries (abc2xml as well as xml2abc). Stay well and healthy, Eckard.
-
well, after copying the LangPack folder to the working directory of the project, I of curse do not get the error message of the missing file idToCharacter.* but still get the crash
-
Hello Eckard, after downloading the patched binaries created on 23rd Dec and the latest SVN dump from 30th Dec I'm not able to generate any NSD any more. While abc2xml is running through the C sources and generates xml files, a call to xml2abc with an NSD configuration informs about the missing itToCharacter.xml and crashes load configuration-file added under configuration root called "Configuration" the new sub-node : <UserArgument> <LogRoot value=".\result\log"/> <RootPath value="A:\tools\Moritz\distribution\Moritz\Development\Moritz_Dev"/>...
-
Hello Eckard, after downloading the patched binaries created on 23rd Dec and the latest SVN dump from 30th Dec I'm not able to generate any NSD any more. While abc2xml is running through the C sources and generates xml files, a call to xml2abc with an NSD configuration informs about the missing itToCharacter.xml and crashes %MORITZ_PATH%\bin\xml2abc UA:LogRoot=%MORITZ_LOG_PATH% UA:RootPath=%MORITZ_PATH% UA:ResultPath=%MORITZ_RESULTS% CF.\cfg\ansi_c_xml2abc_cfg_nsd.xml > %MORITZ_LOG_PATH%\log_xml2abc_nsd.log...
-
Hello Eckard, after downloading the patched binaries created on 23rd Dec and the latest SVN dump from 30th Dec I'm not able to generate any NSD any more. While abc2xml is running through the C sources and generates xml files, a call to xml2abc with an NSD configuration informs about the missing itToCharacter.xml and stops. load configuration-file added under configuration root called "Configuration" the new sub-node : <UserArgument> <LogRoot value=".\result\log"/> <RootPath value="A:\tools\Moritz\distribution\Moritz\Development\Moritz_Dev"/>...
-
#if ( ... ) fails
-
assembler support
-
PS.: Some seconds ago I have uploaded a new SVN archive that contains all changes I have implemented in the last days as result of our discussions. You will find it here.
-
Moritz released /Moritz_2.x/DevelopmentFor_2_1_0/TemporaryFolder/Archiev_SVN_2020_12_30.zip
-
Hello Wasili. Actually XML files ending with _code.xml should only be created as a debugging output if the following configuration files contain a command for doing this. [Moritz_Root]\LangPack\ansi_c\a2x\abc2xml_Process_ansi_c_only.xml [Moritz_Root]\LangPack\ansi_c\a2x\abc2xml_Process_ansi_cpp.xml * The one that is really important for you depends on the one you mention in the last line of the configuration file used to list the files and/or folders to parse. Please search for the following lines...
-
Hello Wasili. As already mentioned above I have set up a new topic User Extension of the C/Cpp Grammar for Inline-Assembler in the development discussion . Here I posted a first trial to solve your issue regarding your inline assembler. Please use from now this development forum topic to discuss this issue. Note: Since I'm not really familiar with inline-assembler, the current user-grammar syntax-rules are sufficient to parse your small example but may struggle by other inline-assembler lines used...
-
This topic should continue the discussion of the bug #21 assembler support reported by Wasilios Goutas. In the his code inline assembler is used that is actually not supported by Moritz. It is not possible to extend the parser grammar with a standard solution working for all thinkable cases, since the coding of inline-assembler is very compiler specific and the assembler mnemonics are depending on the hardware-platform the code is written for. Thus the solution has to be implemented as user specific...
-
Hello Wasili. As already mentioned above I have set up a new topic User Extension of the C/Cpp Grammar for Inline-Assembler in the development discussion . Here I posted a first trial to solve your issue regarding your inline assembler. Please use from now this development forum topic to discuss this issue. Note: Since I'm not really familiar with inline-assembler, the current user-grammar syntax-rules are sufficient to parse your small example but may struggle by other inline-assembler lines used...
-
Dear Users. This topic should continue the discussion of the bug #10 preprocessor directive issue reported by Wasilios Goutas. In the his code some preprocessor definitions are used to insert compiler specific attributes in data declarations and data definitions. The preprocessor defintions are used instead of the real attribute-syntax to clean up the code. But since Moritz has no preprocessor that is replacing the preprocessor defintions by the real attribute-syntax the parser is struggeling by...
-
Hello Eckard, I downloaded the latest Moritz snapshot from 23rd Dec 20 and the patched binaries xml2abc Version 2.1.0 generation of nassi shneiderman diagrams for source-codes Copyright (C) 2004-2020 by Eckard Klotz Build date: Dec 23 2020 , time: 13:05:37 Build as : 64 bit application but when using this combination all files been processed by abc2xml create ..._c_code.xml files are 32Byte long and contain the same content <Content L="1" C="1"></Content> Even when making use of the old binaries...
-
Hello Eckard, I found a way to make use of the patch from 23rd Dec. 20. The reproducer is working with the new binaries and the configuration files you provided. Unfortunately the output of the sources I'm working on is behaving different. I tested the changes with both binary versions (the one from 10th June and the new one of 23.Dec) and the results I get now is, that all sources of my source tree result in xml files called ...filename...c_code.xml contain nothing but the following <Content L="1"...
-
Hello Wasili. The coding of inline-assembler is very compiler specific. Some are doing it with a function like syntax others with pragma directives. I never saw your approach before. However this is something that could not be supported by a standard solution. Thus I would not accept this as a bug. Your idea to solve this with the user-grammar is the only possible solution. But we have to introduce a new rule (perhaps some more) to solve this problem. Just extending the user-attribute will not help....
-
Hello Wasili. The coding of inline-assembler is very compiler specific. Some are doing it with a function like syntax others with pragma directives. I never saw your approach before. However this is something that could not be supported by a standard solution. Thus I would not accept this as a bug. Your idea to solve this with the user-grammar is the only possible solution. but we have to introduce a new rule (perhaps some more) to solve this problem. Just extending the user-attribute will not help....
-
int16_t not supported (but uint16_t is)
-
brackets confusing the parser
-
Hello Wasili. To solve this issue I have to provide a new configuration file. This patch should should solve your issue " brackets confusing the parser ". Please check the attached file with your virus scanner before you use it to replace the one with the same name in the bin folder of your Moritz distribution. Replace with the attached file "ANSI_C_Source_C_only_grm.a2x" the one with the same name in your Moritz distribution sub folder "[MoritzRoot]\LangPack\ansi_c\a2x\". It may be useful to keep...
-
Hello Wasili. To solve this issue I have to provide a new configuration file. This patch should should solve your issue " int16_t not supported (but uint16_t is) ". Please check the attached file with your virus scanner before you use it to replace the one with the same name in the bin folder of your Moritz distribution. Replace with the attached file "ANSI_C_Source_C_only_grm.a2x" the one with the same name in your Moritz distribution sub folder "[MoritzRoot]\LangPack\ansi_c\a2x\". It may be useful...
-
int16_t not supported (but uint16_t is)
-
Hello Wasili. To solve this issue I have to provide a new configuration file. This patch should should solve your issue " brackets confusing the parser ". Please check the attached file with your virus scanner before you use it to replace the one with the same name in the bin folder of your Moritz distribution. Replace with the attached file "ANSI_C_Source_C_only_grm.a2x" the one with the same name in your Moritz distribution sub folder "[MoritzRoot]\LangPack\ansi_c\a2x\". It may be useful to keep...
-
assembler support
-
int16_t not supported (but uint16_t is)
-
brackets confusing the parser
-
Hello Wasili. I have tested your examples with the newest Moritz patch published on 2020-12-23 together with the patch I have provided to solve your issue struct initializer with condition But I was not able to reproduce your issue. I don't want to add the complete XML output here but as far as I can see every path of your compiler-switch is present including the error-directive. The Nassi Shneiderman diagram for it looks like this: test ( ) int test ( ) PREPROSESSOR ALTERNATIVES PREPROSESSOR DEFAULTS...
-
Hello Wasili. I have tested your examples with the newest Moritz patch published on 2020-12-23 together with the patch I have provided to solve your issuestruct initializer with condition But I was not able to reproduce your issue. I don't want to add the complete XML output here but as far as I can see every path of your compiler-switch is present including the error-directive. The Nassi Shneiderman diagram for it looks like this: test ( ) int test ( ) PREPROSESSOR ALTERNATIVES PREPROSESSOR DEFAULTS...
-
#if ( ... ) fails
-
struct initializer with condition
-
Hello Wasili. To solve this issue I have to provide new configuration files. This patch should should solve your issue "struct initializer with condition ". Please check the attached files with your virus scanner before you use it to replace the one with the same name in the bin folder of your Moritz distribution. Replace with the attached file "ANSI_C_Source_C_only_grm.a2x" the one with the same name in your Moritz distribution sub folder "[MoritzRoot]\LangPack\ansi_c\a2x\". Replace with the attached...
-
brackets confusing the parser
-
reproduser attached
-
#if ( ... ) fails
-
reproduser attached
-
struct initializer with condition
-
initializing array failed
-
#if 1 not supported
-
abc2xml configured to parse single file failes on include statement
-
Hello Wasili. I assume that the source you have faced effect contains an additional problem that actually results in your issue. This may be a special comment or a declaration directly behind the include line. Furthermore I assume that "anyHeaderh" is not what you really use in your case. However, as long as you are not able to provide me more information I could not evaluate and fix your issue. Please reopen this bug-discussion once you face the issue again and are able to provide more details ideally...
-
Thanks Eckard, I tested it and it works BR Wasili
-
Thanks Eckard, I tested it and it works
-
Hello Eckard, on my system is a mixture of Moritz binaries from June 2020 and configuration files from the SVN repository from November I think. Maybe the behavior on my system is caused by this. If on your system it is working as expected than its fine. I don't need this functionality by now. BR Wasili
-
Hello Jeridiah Welti. It is difficult for me to examine your problem just by your description but without any knowing your project details. If I understand you right, you not only miss the des files but you miss all generated by xml2abc associated with the files you have added to the configuration of the Moritz demo-project. The only files you get for them are the xml files generated by abc2xml for them. Thus I don't think that I really have to mention that des files will only be generated if you...
-
initializing array failed
-
Hello Wasili. To solve this issue I have to provide a new configuration file. This patch should should solve your issue " initializing array failed ". Please check the attached file with your virus scanner before you use it to replace the one with the same name in the bin folder of your Moritz distribution. Replace with the attached file "ANSI_C_Source_C_only_grm.a2x" the one with the same name in your Moritz distribution sub folder "[MoritzRoot]\LangPack\ansi_c\a2x\". It may be useful to keep the...
-
initializing array failed
-
abc2xml configured to parse single file failes on include statement
-
#if 1 not supported
-
Hello Wasili. To solve this issue I have to provide a new configuration file. This patch should should solve your issue "#if 1 not supported ". Please check the attached file with your virus scanner before you use it to replace the one with the same name in the bin folder of your Moritz distribution. Replace with the attached file "ANSI_C_Expression.a2x" the one with the same name in your Moritz distribution sub folder "[MoritzRoot]\LangPack\ansi_c\a2x\". It may be useful to keep the old files for...
-
#if 1 not supported
-
Jeridiah Welti posted a comment on discussion Help
What would prevent Moritz xml2abc to not generate a des file? I have been trying to bootstrap a new project, and for some reason I cannot get it to parse my files completely. It runs the example code fine, but any files I add to the src folder do not get fully parsed. It appears to create XML files for them, but not dot files. Looking in the des folder the only files I see are the samples. ansi_c_xml2abc_cfg_uad.xml is looking only at the folder and is not listing specific files so I'm not sure why...
-
initializing array failed
-
#if 1 not supported
-
Hello Wasili. I added in one of my demo files which are called as single files also your include-line as first line. The parser abc2xml had no problem with it and the associated content of the produced file is this: <preprocedure c="1" l="1"> <p_include c="1" l="1"> <keychr c="1" l="1">#</keychr> <keyword c="2" l="1">include</keyword> <p_text c="10" l="1">"anyHeaderh" </p_text> </p_include> </preprocedure> You wrote: I noticed that the first ... Could it be that I have misunderstood you? Please provide...
-
Hello Wasili. I added in one of my demo files which are called as single files also your include-line as first line. The parser abc2xml had no problem with it and the associated content of the produced file is this: <preprocedure c="1" l="1"> <p_include c="1" l="1"> <keychr c="1" l="1">#</keychr> <keyword c="2" l="1">include</keyword> <p_text c="10" l="1">"anyHeaderh" </p_text> </p_include> </preprocedure> You wrote: I noticed that the first ... Could it be that I have misunderstood you? Please provide...
1 >