[M3devel] [M3commit] CVS Update: cm3
Jay K
jay.krell at cornell.edu
Tue Dec 1 09:43:10 CET 2009
Interest in Interix would probably track similarly with interest in Cygwin.
They each have pluses and minuses.
Interix in particular has a "normal" fast fork and is therefore far less unpleasant to use, esp. building m3cc.
(Tip for Interix users: "net stop beep". I find Interix beeps a lot and the volume can't be controlled or muted (using the normal methods), such as when tab doesn't have anything to complete, etc.)
- Jay
From: hosking at cs.purdue.edu
Date: Mon, 30 Nov 2009 13:21:39 -0500
To: hendrik at topoi.pooq.com
CC: m3devel at elegosoft.com
Subject: Re: [M3devel] [M3commit] CVS Update: cm3
I was really just asking what the Interix target was good for. Windows users will want Windows integration, right? Rather than the Interix hybrid...
On 30 Nov 2009, at 11:05, hendrik at topoi.pooq.com wrote:
On Mon, Nov 30, 2009 at 09:48:48AM -0500, Tony Hosking wrote:
This whole interix thing is pretty messy. Why do we care? If you are on Windows just use Windows threads. No need to pollute the pthreads code base with unnecessary complications for weird hybrids.
There seems to be a campaign to make all OS's behave the same to the
lowest possible code level. The only way to do that is to restrict
ourselves to a subset of their facilities that all share. I suspect
this is too restrictive. For popular platforms, at least, we should be
open to implement Modula 3 library features in a way that takes
advantage of those platforms peculiar abilities -- provided that the
library-user facilities remain compatible of course.
That said, Windows is a popular platform that I have no use for (Windows
won't even install on my most-used machine -- for some obscure reason
it will only run in maintenance mode; my daughter says the machine is
corsed). The only thing I need Windows for is writing programs that
are to uised by other people. For that purpose, I do care that any
Modula 3 applications I write can be cross-compiled (ideally) and
immediately run properly on Windows without modification.
But I suspect that is too much to expect in the real world, even with
the uncanny competence with which Modula 3 system is put togeter.
-- hendrik
On 30 Nov 2009, at 13:03, Jay Krell wrote:
CVSROOT: /usr/cvs
Changes by: jkrell at birch. 09/11/30 13:03:07
Modified files:
cm3/m3-libs/m3core/src/thread/PTHREAD/: ThreadPThread.m3
Log message:
keep two thread handles
what to call them is unclear
here we ahve:
joinHandle
suspendResumeHandle
aka:
pthread
ntthread
on all but Interix (and possibly Cygwin), they are equivalent,
either the result of pthread_create or pthread_self
on Interix, once is pthread_create/self, the other is a kernel handle
for suspend/resume
alternate names welcome
the intent seems hoky, but helps much
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20091201/3829999d/attachment-0002.html>
More information about the M3devel
mailing list