Re: [ tidy-Patches-1551769 ] memory mapping on win32

Tuesday, 19 September 2006.

Hi Charlie,

Thanks for the email ...

Sometimes it is not really a 'preference' for MSVC6, but that may be all 
they have, given the COST of buying Microsoft's build tools ;=)) Yes, the 
Express version 8 is presently FREE for the download, but it does NOT 
include modifying resources (RC) files, so is partially 'broken' ...

ADDED to that is the fact that the MSVC6 DSW/DSP files can be loaded, 
converted, and used by ALL later products, making it the best single choice 
for open projects ... lots now also include 7.1 and/or 8 'solution' files, 
but this, IMHO, just makes for more source upkeep with no appreciable gain 
...

I too mainly use 7.1, since 8 also make 'sharing' binary EXE much harder ... 
it embeds a need for its own 'special' runtime libraries, which can no 
longer be simply 'copied' to other machines, thus you usually have to ship 
it all in a MSI installer file, otherwise there is a good chance it will not 
run ...

There is still one tiny 'bug' in the tidydll.dsp file that causes it not to 
load, but I am sure this will be 'fixed' in cvs shortly ... the small diff 
is -

<diff>
--- F:\FGCVS\tidy\build\msvc\tidydll.dsp	Tue Sep 19 15:45:44 2006
+++ tidycvs6-1\build\msvc\tidydll.dsp	Tue Sep 19 16:22:31 2006
@@ -183,7 +183,7 @@

SOURCE=..\..\src\utf8.c
# End Source File
-# End Group
+# Begin Source File

SOURCE=..\..\src\win32tc.c
# End Source File
</diff>

Just one line changed from # End Group to # Begin Source File. With this 
patch in place I was able to build Tidy with MSVC6, MSVC7.1 and MSVC8 all 
from tidy.dsw, plus dsps ...

Of course you get some very UGLY 'depreciation' warnings from MSVC8 unless 
you add _CRT_SECURE_NO_DEPRECATE to the preprocessor defines, and an error 
unless you disable the embedding of the 'manifest' in Debug, and that still 
leaves some big ugly C4996 warnings - like -

<warning>
tidylib.c
f:\gtools\tidyproj\tidycvs8\src\tidylib.c(1003) : warning C4996: '_setmode' 
was declared deprecated
        c:\program files\microsoft visual studio 8\vc\include\io.h(228) : 
see declaration of '_setmode'
        Message: 'The POSIX name for this item is deprecated. Instead, use 
the ISO C++ conformant name: _setmode. See online help for details.'
</warning>

I guess MS does not want to follow the POSIX conventions for things like 
'setmode', and 'access', used in Tidy, but also for open, close, etc, etc 
... and CLAIMS ISO C++ conformance instead ... I thought POSIX drove ISO, 
but do not know enough about this type of compiler 'politics' to care ;=))

When the cvs settles down, I will again try my patch for the "malformed 
inline
tags", but I guess this was not liked, i.e. not cvs accepted, because to do 
it I must 'manipulate' the internal tag stack - much more than just push and 
pop! ...

But on the other hand, accepting such 'tag-stack-changes' would open up 
other areas that Tidy could work in ... such that Tidy's output is rendered 
by the browser the SAME as the original ... one bug I remember was a 
'broken' form with input tag, which could be likewise 'fixed' by Tidy, IFF 
...

Anyway, I will re-do it, over time, and research a little more what could be 
done with such capability ... and update my web pages likewise ...

Have FUN!

Geoff.

EOF - Tidy-46.doc

_________________________________________________________________
Don't just search. Find. Check out the new MSN Search! 
http://search.msn.click-url.com/go/onm00200636ave/direct/01/


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV