Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Received-SPF: pass (nike.apache.org: domain of fraser.adams@blueyonder.co.uk
 designates 80.0.253.73 as permitted sender)
Message-ID: <5273A277.8060404@blueyonder.co.uk>
Date: Fri, 01 Nov 2013 12:45:43 +0000
From: Fraser Adams <fraser.adams@blueyonder.co.uk>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: users@qpid.apache.org
Subject: Re: In proton Is protocol.py actually called anywhere?
References: <52738133.6040602@blueyonder.co.uk>
 <CACL1BnDKWE3Zc2SdcOH0kxktizemaBMgqfqdrBy0+ySJ+=AD9A@mail.gmail.com>
In-Reply-To: 
 <CACL1BnDKWE3Zc2SdcOH0kxktizemaBMgqfqdrBy0+ySJ+=AD9A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Thanks Rafael,
I'd noticed protocol.h.py and encodings.h.py and the stuff in 
CmakeLists.txt, but was too busy grepping for specific file names to notice

  "from protocol import *" in protocol.h.py, d'Oh

:-D

cheers,
Frase


On 01/11/13 11:45, Rafael Schloming wrote:
> They are called from the build system. Lines 63 through 74 of
> proton-c/CMakeLists.txt add a custom command to call both protocol.h.py and
> encodings.h.py as part of the build process. These scripts pick through the
> xml files and produce header files with useful #defines. The protocol.py
> module is imported by protocol.h.py as part of this.
>
> We don't currently use transactions.xml yet, but it is part of the xml that
> comes with the spec. I expect we'll start using it as soon as we build out
> better transaction support in the APIs.
>
> --Rafael
>
>
> On Fri, Nov 1, 2013 at 6:23 AM, Fraser Adams
> <fraser.adams@blueyonder.co.uk>wrote:
>
>> Hi All,
>> I've been trying to stumble my way round the proton directory tree trying
>> to work out how the Cmakes hang together and the like.
>>
>> Now I can see protocol.h.py gets called but when I grepped for
>> protocol.py (grep -rH "protocol.py" .) I got:
>> Binary file ./proton-c/src/protocol.pyc matches
>> ./proton-c/src/.svn/all-**wcprops:protocol.py
>> ./proton-c/src/.svn/all-**wcprops:/repos/asf/!svn/ver/**
>> 1352267/qpid/proton/trunk/**proton-c/src/protocol.py
>> ./proton-c/src/.svn/entries:**protocol.py
>>
>> So it doesn't look like it's called from anywhere - same for protocol.pyc
>>
>> Similarly it looks like messaging.xml, transport.xml, security.xml are
>> only called from protocol.py and I can't see anywhere transactions.xml is
>> referenced?
>>
>> I guess it's possible that these are referenced via dynamically
>> constructed names that I can't see by grepping.
>>
>>
>> Curious to know if they are there for a reason or are currently redundant.
>>
>> (This is me looking in trunk )
>>
>> cheers,
>> Frase
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.**org<users-unsubscribe@qpid.apache.org>
>> For additional commands, e-mail: users-help@qpid.apache.org
>>
>>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org