>
> 1. select() in Windows only works on sockets. I had previously fudged my
> way around this with some WaitForMultipleObjects hacks, but I've not yet
> figured out how to emulate select() on Windows in a way which works for
> stdio, pipes *and* sockets, and the latest cothread won't work without
> support for pipes (though I'm willing to fake this as appropriate). Alas,
> I've not take the time to figure this out, and it does not seem
> straightforward.
Don't know of any solution. I am moving away from select in general, and handling things with extra threads that just block BTW.
>
> 2. Compiling on Windows is nasty. VC++ doesn't support C99, and its
> assembler syntax is somewhat different, but it would seem that mingw is
> very much a moving target. Last time I tried a ming32 build I ended up
> hacking my Python.h files to get things working and then stopped in
> disgust.
I have had good success with mingw. The visual C++ debugger is actually pretty good IMHO, but unfortunately MS has a long history of being a bit slow to adopt international standards. Maybe they are too busy hacking on C#.
>
> It is probably better to bite the bullet and create VC compatible versions
> of the files in the context/ directory, but I am so reluctant...
>
> 3. From spring this year it will have been exactly a decade since I was
> last employed as an engineer to work on Windows. I rejoice. Sorry, but
> this is my attitude to the platform. I don't want to say much more, as
> I'm liable to rant at this point!
>
>
> > And, sorry for the questions, but I've always been a little confused
> > by cothread. Perhaps you could clarify some points for me?
>
> I'll answer this in another e-mail, would like to separate the Windows
> issue from the rest!
>
> --
> This e-mail and any attachments may contain confidential, copyright and or
> privileged material, and are for the use of the intended addressee only.
> If you are not the intended addressee or an authorised recipient of the
> addressee please notify us of receipt by returning the e-mail and do not
> use, copy, retain, distribute or disclose the information in or attached
> to the e-mail.
> Any opinions expressed within this e-mail are those of the individual and
> not necessarily of Diamond Light Source Ltd.
> Diamond Light Source Ltd. cannot guarantee that this e-mail or any
> attachments are free from viruses and we cannot accept liability for any
> damage which you may sustain as a result of software viruses which may be
> transmitted in or with the message.
> Diamond Light Source Limited (company no. 4375679). Registered in England
> and Wales with its registered office at Diamond House, Harwell Science and
> Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
>
>
>
>
- Replies:
- RE: Invitation to test cothread.catools release candidate michael.abbott
- References:
- Invitation to test cothread.catools release candidate michael.abbott
- Re: Invitation to test cothread.catools release candidate Matt Newville
- RE: Invitation to test cothread.catools release candidate michael.abbott
- Navigate by Date:
- Prev:
Re: Channel Access Paul Sichta
- Next:
SmarAct / SmarPod Gofron, Kazimierz
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
<2012>
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: Invitation to test cothread.catools release candidate michael.abbott
- Next:
RE: Invitation to test cothread.catools release candidate michael.abbott
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
<2012>
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|