<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>What is the idiom for this:<BR>
<BR>
Currently:<BR>
There is Pathname.i3.<BR>
PathnamePosix EXPORTS Pathname<BR>
PathnameWin32 EXPORTS Pathname<BR>
You can only have one in a link.<BR>
<BR>
It would seem possibly useful to have:<BR>
Pathname.i3 unchanged<BR>
PathnamePosix.i3 identical to Pathname.i3 (some what to avoid the duplication?)<BR>
PathnameWin32.i3 identical to Pathname.i3 (ditto)<BR>
<BR>
On Posix targets:<BR>
PathnameWin32.m3 exports just PathnameWin32<BR>
PathnamePosix exports both PathnamePosix and Pathname<BR>
<BR>
On Windows targets:<BR>
PathnamePosix exports just PathnamePosix<BR>
PathnameWin32 exports both PathnameWin32 and Pathname<BR>
<BR>
That is Pathname.Foo resolves statically at compile time to the target-specific library.<BR>
PathnameWin32.Foo and PathnamePosix.Foo are also both explicitly available.<BR>
<BR>
These modules each import nothing, except Text. They do all their string manipulation themselves.<BR>
<BR>
Olaf's recent Quake extensions document but don't implement<BR>
pn_native( pn ) --> text<BR> pn_posix( pn ) --> text<BR> pn_win( pn ) --> text<BR><BR>
As long as pn is a fullpath, these are easy, I just wrote up prototypes, haven't compiled them.<BR>
<BR>
I think these functions might suggest doing what I'm asking about as well, maybe.<BR>
Or maybe you'd just convert and then never pick back apart.<BR>
<BR>
I have sleazed by for now by using subst_text / to \ and setting up NTFS junctions.<BR>
In this way, I can cross build NT386 <=> NT386GNU either host, either target.<BR>
Had I not done anything, the linker interprets /cygdrive/c/foo/bar.lib as a command switch and says it doesn't understand it.<BR>
Not a big deal, but I think there might be some easy progress here.<BR>
<BR>
This is not just about Pathname.<BR>
<BR>
It is also about File.<BR>
Even though NT386GNU File is FilePosix, it would be useful to allow the serial package to use FileWin32 instead.<BR>
But FilePosix and FileWin32 both reveal the same types.<BR>
It'd be nice if they could expose FilePosix.T and FileWin32.T and then only one of them reveal File.T = FilePosix.T or File.T = FileWin32.T, something like that.<BR>
<BR>
<BR>
- Jay<BR><br /><hr />Climb to the top of the charts! Play the word scramble challenge with star power. <a href='http://club.live.com/star_shuffle.aspx?icid=starshuffle_wlmailtextlink_jan' target='_new'>Play now!</a></body>
</html>