Comments on: when the problem is likely a bug in the linker…

By: MacPlusG3

MacPlusG3 — Mon, 01 Sep 2008 11:11:48 +0000

why of course it can be OS X. Let’s start with fsync() :)

By: LinuxJedi

LinuxJedi — Fri, 29 Aug 2008 08:16:31 +0000

I’m in favour, but then what can we hurl abuse at? OS X?

By: MacPlusG3

MacPlusG3 — Fri, 29 Aug 2008 08:13:06 +0000

i vote we instead just blast windows off the face of the earth and drink in celebration.

By: LinuxJedi

LinuxJedi — Fri, 29 Aug 2008 08:05:21 +0000

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! :)

By: MacPlusG3

MacPlusG3 — Fri, 29 Aug 2008 02:24:07 +0000

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.

By: MacPlusG3

MacPlusG3 — Fri, 29 Aug 2008 02:23:05 +0000

Yes, very, very unclean. No matter how hard I scrub, it’s just so hard to get it off.

By: LinuxJedi

LinuxJedi — Thu, 28 Aug 2008 15:04:50 +0000

Is all this Windows porting making you feel unclean yet?

By: Antony Curtis

Antony Curtis — Thu, 28 Aug 2008 13:38:53 +0000

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…

By: TimC

TimC — Thu, 28 Aug 2008 12:53:59 +0000

That’s funny. I was thinking *exactly* the same thing.

By: MacPlusG3

MacPlusG3 — Thu, 28 Aug 2008 12:52:35 +0000

*i’m* not the one….

oh wait, what was *i* thinking… well, i am thinking about more whisky…