htod

[simendsjo]

On 12.08.2011 11:24, Jonathan M Davis wrote:
> On Friday, August 12, 2011 04:07:47 Jason King wrote:
>> I'm attempting to convert a c header to d using htod.  If this is not
>> current best practice please point me in another direction.
>>
>> C:\dir>htod -I c:\d\dm\include ocilib.h
>> Fatal error: unable to open input file 'stdlib.h'
>>
>> C:\dir>dir c:\d\dm\include\stdlib.h
>>    Directory of c:\d\dm\include
>>
>> 07/28/2011  09:10 PM            12,553 stdlib.h
>>                  1 File(s)         12,553 bytes
>>                  0 Dir(s)  526,794,256,384 bytes free
>>
>> Putting stdlib.h in same dir with header I'm converting gives no joy either.
>
> There's nothing wrong with using htod if you can get it to work. However, the
> question is whether you can get it to work for what you're doing. And as I
> understand it, you're gonig to have to go over what it did after it did it,
> because it doesn't do a perfect job. But if you can get it to work, it's
> definitely desirable, since it'll save you a fair bit of work.
>
> But unfortunately, htod Windows-only, and I haven't been converting much C
> code lately, I don't know it well enough to really help you get it working. It
> _is_ worth using though.
>
> - Jonathan M Davis

htod is a fork of dmc or something, right? How difficult is it to update 
the program to make it more user friendly?
Is the source public? Would it be better to use gcc or clang instead?
htod is a great thought, but I haven't either gotten it to work for 
anything but the simplest cases.