[mercury-users] [feature request] (slightly) richer XML doc output

Peter Ross pro at missioncriticalit.com
Thu Apr 19 11:37:02 AEST 2007


On 4/18/07, doug.auclair at logicaltypes.com <doug.auclair at logicaltypes.com> wrote:
> Dear Peter, you wrote:
>
> >Yes I wouldn't include those modules because they aren't used in the
> >current module.
>
> Hm, okay.  So, perhaps, instead of discarding the include_module
> elements, is it possible to include those elements into the XML document,
> but annotate them with a <not_used_in_implementation/> child or some
> such?  The XMLer system is so complete that I would dislike needing
> to duplicate parts of it to tease out library-like information.
>
I thought I didn't have the information but I do.

Here is the format

    <imports>
        <import>
            <qualified>
                <module>parse_tree</module>
                <name>source_file_map</name>
            </qualified>
            <visibility>implementation</visibility>
        </import>
        <import>
            <qualified>
                <module>parse_tree</module>
                <name>prog_data</name>
            </qualified>
            <visibility>implementation</visibility>
        </import>
        <import>
            <unqualified>io</unqualified>
            <visibility>interface</visibility>
        </import>
    </imports>
--------------------------------------------------------------------------
mercury-users mailing list
Post messages to:       mercury-users at csse.unimelb.edu.au
Administrative Queries: owner-mercury-users at csse.unimelb.edu.au
Subscriptions:          mercury-users-request at csse.unimelb.edu.au
--------------------------------------------------------------------------



More information about the users mailing list