Re: Tidy Porting issues

What are the chances that any of these ideas about restructuring Tidy (for
use in a library) will be implemented anytime soon?  I'd rather not hack
into Tidy on my own until things are stable on the "Official Release" end of
things.  If there won't be many significant structural changes anytime soon,
I'll go ahead and start hacking away.  But if there will be, I've got
another project that I could bump up on the priority queue and work on for a
little while...

Thanks to Terry and Dave for their support.

-----Original Message-----
From: Terry Teague <teague@macbroker.com>
To: html-tidy@w3.org <html-tidy@w3.org>
Date: Saturday, July 10, 1999 7:01 PM
Subject: Tidy Porting issues


>Dear Folks,
>
>As promised earlier, here is a list of issues I have run into while porting
>"tidy" to Mac OS, with the hope that maybe Dave can make changes to the
>base source code to make my (and possibly other peoples') life easier.
>
>1) Minor bugs in the "tidy" base source code :
...
>2) Platform OS/Development Environment specific porting issues :
>(a) in platform.h, newer versions of "tidy" do :
> #include <malloc.h>
...
>(b) Because I take advantage of pre-compiled headers for the Mac OS
> typedef struct _style Style;
>conflicts with the Mac OS ToolBox Text Style structure. I changed the line
to :

...
>I believe one of the first problems I ran into was an apparent non-portable
> #define BLKHDR   16
>I changed this to :
> #define BLKHDR   sizeof(struct _memlink) - sizeof(uint) /* TRT */

...
>(e) Line termination :
...
>3) Application Environment specific porting issues :
>(a) "stdio" :

...
>(b) Command-line interface :
...
>(c) Global variables :

Received on Tuesday, 13 July 1999 13:32:53 UTC