[Cython] Utility Codes and templates

mark florisson markflorisson88 at gmail.com
Fri Jul 22 16:57:51 CEST 2011


On 22 July 2011 16:49, Stefan Behnel <stefan_ml at behnel.de> wrote:
> mark florisson, 22.07.2011 16:13:
>>
>> On 22 July 2011 16:08, Stefan Behnel wrote:
>>>
>>> Stefan Behnel, 22.07.2011 15:54:
>>>>
>>>> However, given that you always need to express metadata in some way
>>>> (e.g.
>>>> for dependencies), I don't think you can do better than with two levels
>>>> anyway, so a third won't hurt *that* much.
>>>
>>> Actually, I take that back. Two levels are easy (think of Windows-INI
>>> style
>>> files), three levels start to get tricky.
>>
>> Fortunate that it is two levels then.
>
> BTW, what about actually using an ini style file format? Something like the
> following may work, but I guess RawConfigParser won't be able to properly
> pass through the C code...
>
> Stefan
>
>
> [utilitycode]
> export=MyCode1,MyCode2
>
> [MyCode1]
> depends=file1:OtherCode1,file1:OtherCode2,MyCode2
>
> [MyCode2]
> depends=file2:OtherCode3
>
> [MyCode1:proto]
> static void ...(); /*proto*/
>
> [Mycode2:proto]
> static int ...(); /*proto*/
>
> [Mycode2:impl]
> static int ...() {
> ...
> }
>
> [Mycode1:impl]
> static void ...() {
> ...
> }

I prefer comments, in .pyx files you use # and in .c files you use //.
Works nicely with syntax highlighting.

> _______________________________________________
> cython-devel mailing list
> cython-devel at python.org
> http://mail.python.org/mailman/listinfo/cython-devel
>


More information about the cython-devel mailing list