when the problem is likely a bug in the linker…
Windows FAIL.
It has been suggested the current thing I’m trying to fix is actually a bug in the Microsoft linker…. and I’m quite willing to believe that.
I wonder if I can expense rehab if this Windows port leads to a drinking problem….
August 28th, 2008 at 10:50 pm
Gah! Windows port!
I much prefer tawny. But even then. Windows port? What were you thinking?!
August 28th, 2008 at 10:52 pm
*i’m* not the one….
oh wait, what was *i* thinking… well, i am thinking about more whisky…
August 28th, 2008 at 10:53 pm
That’s funny. I was thinking *exactly* the same thing.
August 28th, 2008 at 11:38 pm
May not entirely be the linker’s fault… can be a programmer error.
Windows does some of the most arse-backwards things to support dynamic link libraries… The trouble comes because so few people understand the reason why they chose to solve the issues in their special way…
August 29th, 2008 at 1:04 am
Is all this Windows porting making you feel unclean yet?
August 29th, 2008 at 12:23 pm
Yes, very, very unclean. No matter how hard I scrub, it’s just so hard to get it off.
August 29th, 2008 at 12:24 pm
and why couldn’t they have just chosen sane ways to do things… honestly, beyond a year or three, who will care about some weird backwards compat tihng anyway.
August 29th, 2008 at 6:05 pm
Just think, it could be worse… actually scrap that…
You do know of course that now you are porting cluster us guys that code cluster tools are going to have to port as well! :)
August 29th, 2008 at 6:13 pm
i vote we instead just blast windows off the face of the earth and drink in celebration.
August 29th, 2008 at 6:16 pm
I’m in favour, but then what can we hurl abuse at? OS X?
September 1st, 2008 at 9:11 pm
why of course it can be OS X. Let’s start with fsync() :)