Hey,
The conclusion from the python3 IRC discussion:
> Debian and Debian based distributions do not load the Python 3 shared library
> into memory, so it is necessary to link statically with the **Python.h**
> header.
Lesson learned.
As a side note, why do we need enum names in RTTI unconditionally?
You're right, your module's `getType` was used. Just to be used in type
annotations it should not be immediate - should either have typed arguments or
be overloaded. Adding some proc (template, ...) like `proc getType = discard`
makes `import macros` unneeded - that was just coincidence, that it
[인천오피]강남오피[WWW.OPSS3.COM 오피쓰]부천오피[강남건마] [인천오피]강남오피[WWW.OPSS3.COM 오피쓰]부천오피[강남건마]
[인천오피]강남오피[WWW.OPSS3.COM 오피쓰]부천오피[강남건마] [인천오피]강남오피[WWW.OPSS3.COM 오피쓰]부천오피[강남건마]
[인천오피]강남오피[WWW.OPSS3.COM 오피쓰]부천오피[강남건마] [인천오피]강남오피[WWW.OPSS3.COM 오피쓰]부천오피[강남건마]
[인천오피]강남오피[WWW.OPSS3.COM 오피쓰]부천오피[강남건마]
오피쓰 일산오피 www.opss3.com 강남오피[부천오피]강남건마오피쓰 일산오피 www.opss3.com 강남오피[부천오피]강남건마오피쓰
일산오피 www.opss3.com 강남오피[부천오피]강남건마오피쓰 일산오피 www.opss3.com 강남오피[부천오피]강남건마
I found a way to deal with the problem finally. We cannot define an template
which return an 'type' (sometime it will fail to compile), but if I return a
variable of the type, it is ok, then I can get the type of the variable.
template get_val_from_item(seq1: untyped): untyped =
@LeuGim
One little question. When I import the macros, the getType of this file is
used, not the macros's getType, this is strange. That's mean import macros
affect the template in this file can be used or not.