<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>They'll be escaped.?<BR>Olaf, I'm just not sure. It could be that if I just set CM3_ROOT, CM3_INSTALL, and possibly M3_CONFIG, then the Posix code is ok. However, note as I said that Cygwin does accept these paths..<BR>The opposite problem holds too -- I like copy/pasting the error messages into file.open dialogs, and forward slashes don't work there unfortunately.<BR>
I had a diff for a bit that between \ and /, would try to use whatever was already in the data.<BR>
I had a problem with but it still might be viable, specifically in the Win32 paths.<BR>
<BR>
Maybe if I can just get it definitely usable (maybe already there) and get a distribution out, someone else can hack on this issue..<BR>
<BR>
- Jay<BR><BR>
<HR id=stopSpelling>
<BR>
> Date: Sat, 23 Feb 2008 13:39:09 +0100<BR>> From: wagner@elegosoft.com<BR>> To: m3devel@elegosoft.com<BR>> Subject: Re: [M3devel] paths..<BR>> <BR>> Jay,<BR>> <BR>> I'm not really happy with NT386GNU using PathnameWin32.m3.<BR>> In my opininion it should just use the POSIX code, whatever problems<BR>> people will have with their installation roots. (These can be avoided<BR>> by using the /cygdrive/... equivalents.)<BR>> Why don't we just assume that by deafult CM3 is installed in<BR>> /usr/local/cm3 as for all other targets (except NT386, of course)?<BR>> <BR>> One thing that immediately comes to mind is that all paths output<BR>> by CM3 programs will contain \ instead of / then and thus be<BR>> unusable for simple copy-and-paste, as \ is the escape character<BR>> in all POSIX command line tools. So this seems kind of incompatible<BR>> to me.<BR>> <BR>> Olaf<BR>> <BR>> Quoting Jay <jayk123@hotmail.com>:<BR>> <BR>> > I could be wrong about many things here:<BR>> ><BR>> > Cygwin fopen and I presume open accepts all of:<BR>> > c:\foo, c:/foo, /foo, \foo<BR>> ><BR>> > /foo and \foo probably have a different meaning between Cygwin and Win32.<BR>> > In Win32, /foo and \foo are, well, \foo, on the current drive.<BR>> > In Cygwin, /foo is probably /foo at the Cygwin root.<BR>> > I'd kind of like to be wrong here, about \foo having different <BR>> > meanings between them, since it a common form for me.<BR>> ><BR>> > Cygwin does not accept c:foo.<BR>> > In Win32 c:foo is foo in the current working directory of the C: drive.<BR>> > I don't think c:foo is used often, but it does have a meaning.<BR>> ><BR>> > Now, as well, cm3 has its own Path module, M3Path, but I realized <BR>> > tonight it also uses libm3's Pathname module a fair amount. In <BR>> > particular, I was having errors "shipping".<BR>> ><BR>> > This throws a big monkey wrench into where I was going.<BR>> > So now, after a bunch of going back and forth on various uncommited <BR>> > changes, I have now switched (and commited) NT386GNU to use <BR>> > PathnameWin32.m3. To some extent, this strikes at the core of "what <BR>> > is Posix" and "ruins" NT386GNU's differentiation from "NT386MINGNU". <BR>> > However, remember that Cygwin does appear to accept Win32 paths. <BR>> > So, again, if Cygwin accepts Win32 paths, is it Posix? (Given that <BR>> > Win32 accepts /foo, is it Posix?) As well, this target still uses <BR>> > cygwin1.dll for its all its odd behaviors. It still uses <BR>> > open/read/write (again, remember that msvcrt.dll DOES expose these <BR>> > SAME functions..I still contend that Win32 is close enough to Posix <BR>> > to satisfy almost everyone..and then X Windows can be dealt with <BR>> > separately maybe, or Trestle/Win32 fixed).<BR>> ><BR>> > I have some more testing to do but I think this switch will fly, and <BR>> > various other options can go away.<BR>> > And I can undo the small amount I had commited.<BR>> > I think I'll just send my m3path.m3 diff around and then delete it.<BR>> ><BR>> > I ended up with a set based approach where host and target have a <BR>> > set of dir separaters, volume separaters, and separators (union of <BR>> > previous two). These are TINY sets, containing a maximum of three <BR>> > characters each, and '/' is always a member of two of them. So a set <BR>> > is kind of overkill. But it works out pretty ok.<BR>> ><BR>> > - Jay<BR>> > _________________________________________________________________<BR>> > Need to know the score, the latest news, or you need your <BR>> > Hotmail®-get your "fix".<BR>> > http://www.msnmobilefix.com/Default.aspx<BR>> <BR>> <BR>> <BR>> -- <BR>> Olaf Wagner -- elego Software Solutions GmbH<BR>> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany<BR>> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95<BR>> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin<BR>> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194<BR>> <BR><BR><br /><hr />Connect and share in new ways with Windows Live. <a href='http://www.windowslive.com/share.html?ocid=TXT_TAGHM_Wave2_sharelife_012008' target='_new'>Get it now!</a></body>
</html>