On 2013-12-07 18:53, Andre wrote:
If DStep is the prefered solution would it be possible to also
provide a pre compiled binary for windows? This would make DStep
more user friendly.
=> Just trying to find out what is needed to compile DStep on a
windows machine, whether I need mambo/tango/s.th.
If DStep is the prefered solution would it be possible to also
provide a pre compiled binary for windows? This would make DStep
more user friendly.
=> Just trying to find out what is needed to compile DStep on a
windows machine, whether I need mambo/tango/s.th. else and
praying libclang is availa
On 2013-12-06 19:35, Andrej Mitrovic wrote:
I guess libtooling (http://clang.llvm.org/docs/LibTooling.html) would
be a better fit for a codegenerator, but it's a C++ library.
What would be better is to use the Clang C++ libraries since they
already provide all the functionality needed. Althou
On 2013-12-06 19:35, Andrej Mitrovic wrote:
I guess libtooling (http://clang.llvm.org/docs/LibTooling.html) would
be a better fit for a codegenerator, but it's a C++ library.
I don't see what this would give me. libclang already handles command
line parsing. DStep handles, in addition to thos
On 12/6/13 7:15 AM, Dicebot wrote:
To be honest I'd love htod to be completely removed from
dlang.org (and possibly replaced with dstep) as it does more harm
than good.
I agree. Please send a pull request.
Thanks,
Andrei
On 12/6/13, Jacob Carlborg wrote:
> On 2013-12-06 18:13, Jacob Carlborg wrote:
>
>> It does substitutions. I guess using libclang would be just like
>> compiling with Clang but stop the process somewhere after the AST is
>> created and before the code generating phase has started.
>
> This also ha
On 2013-12-06 18:13, Jacob Carlborg wrote:
It does substitutions. I guess using libclang would be just like
compiling with Clang but stop the process somewhere after the AST is
created and before the code generating phase has started.
This also has the unfortunate consequences that you can onl
On 2013-12-06 18:10, Dicebot wrote:
Does it simply ignores preprocessor tokens or actually makes
substitutions (but there is no D-ification)? I thought it is the latter.
It does substitutions. I guess using libclang would be just like
compiling with Clang but stop the process somewhere after
On Friday, 6 December 2013 at 17:02:18 UTC, Jacob Carlborg wrote:
On 2013-12-06 16:14, Dicebot wrote:
htod is old and unsupported. I recommend dstep
(https://github.com/jacob-carlborg/dstep) which is based on
libclang and
thus naturally up to date with current C state.
DStep doesn't current
On 2013-12-06 16:14, Dicebot wrote:
htod is old and unsupported. I recommend dstep
(https://github.com/jacob-carlborg/dstep) which is based on libclang and
thus naturally up to date with current C state.
DStep doesn't currently support any preprocessor handling, except for
some simple include
To be honest I'd love htod to be completely removed from
dlang.org (and possibly replaced with dstep) as it does more harm
than good.
On Friday, 6 December 2013 at 15:04:18 UTC, Andre wrote:
Hi,
HTOD is not able to translate a #define if the
value is in brackets like here:
#define SQL_STILL_EXECUTING 2
#define SQL_ERROR (-1)
#define SQL_INVALID_HANDLE (-2)
strange, sent once but posted 2 times on server
On Friday, 6 December 2013 at 15:04:58 UTC, Andre wrote:
Hi,
HTOD is not able to translate a #define if the
value is in brackets like here:
#define SQL_STILL_EXECUTING 2
#define SQL_ERROR (-1)
#de
Hi,
HTOD is not able to translate a #define if the
value is in brackets like here:
#define SQL_STILL_EXECUTING 2
#define SQL_ERROR (-1)
#define SQL_INVALID_HANDLE (-2)
#define SQL_NEED_DATA 99
(Examp
Hi,
HTOD is not able to translate a #define if the
value is in brackets like here:
#define SQL_STILL_EXECUTING 2
#define SQL_ERROR (-1)
#define SQL_INVALID_HANDLE (-2)
#define SQL_NEED_DATA 99
(Examp
15 matches
Mail list logo
