PureBasic Forums - English

C:\Program Files\PureBasic\Compilers>polink.exe
Pelles Linker, Version 5.00.1
Copyright (c) Pelle Orinius 1998-2008

There is no reason to use this old version. Win95/98 is 32bit only.

And last but not least:
PellesC 6.50 RC3 is out. Maybe a switch to this newest version should be checked before the 4.60 will be released.

moved, as its not a bug

There is no reason to use this old version.

That's not relevant in my opinion. The relevant question is: is there any reason to use the new version?

As they say: If it ain't broken, don't fix it.

Trond wrote:

There is no reason to use this old version.

That's not relevant in my opinion. The relevant question is: is there any reason to use the new version?

As they say: If it ain't broken, don't fix it.

Interesting question.
I am sure your car is > 10 years old.
Your PC has DOS.
And you have candle lights instead of electric lights.

My hint for you:
You should not update to PureBasic 4.60. Use the 4.51 as long as you life

Better question is: Why is the polink.exe from PellesC 5.0 and the rest from PelesC 6.0 ?

Trond wrote:

There is no reason to use this old version.

That's not relevant in my opinion. The relevant question is: is there any reason to use the new version?

As they say: If it ain't broken, don't fix it.

I'm more of the guys who'd use the latest version whenever it's possible.
Pelles linker has been updated/bugfixed since version 5, that'd be nice to have the new version in Purebasic, even though it might not be a big priority (since it works fine with the current used version).

If the compiler needs or uses something that's in the newest version, then I'm sure the team would update it. But as they haven't, it would indicate that there's no inherent reason to update, except for the sake of updating.

MachineCode wrote:If the compiler needs or uses something that's in the newest version, then I'm sure the team would update it. But as they haven't, it would indicate that there's no inherent reason to update, except for the sake of updating.

It is not really a problem for me. After release of PB 4.60 I will update the polink.exe to the latest one.
Be happy with your candle light.

IceSoft wrote:Be happy with your candle light.

"Don't fix what isn't broken" doesn't apply to candlelight. Candlelight is broken, for all intents and purposes.
But, since you think newer is always better: do you think this car, which is over 10 years old, is no good?
Oh, and a PC with DOS is actually 100% more safe/secure than a Windows PC connected to the internet!

Be happy with your OCD to always have the latest version.

If one of the developers ever reads this: I beg you to update the Pelles Linker!
I made a static library in C++ (VS2010) and when I try to import the .lib or the .obj file to a PB program, the linker just crashes and this shows up:


I like PureBasic, but this doesn't look professional...

Edit: I only tried it with the x86 PB version (yeah I know the title says "[PBx64]") but I think that the same will happen.

Mok wrote:If one of the developers ever reads this: I beg you to update the Pelles Linker!
I made a static library in C++ (VS2010) and when I try to import the .lib or the .obj file to a PB program, the linker just crashes and this shows up:

There is no reason to update polink if the new version doesn't work either. Did you test that?

The team is aware when newer versions become available for components to the PureBasic language. They will update or not based on their judgment so if a component doesn't get updated it doesn't mean they didn't know about it. Listen to Trond on this one, he has it right imho.

Just out of curiosity, could this polink component just be swapped out manually?

I will update PB4.60 to the LATEST (PellesC 6.50) tools which usíng on PureBasic after release of PB.
(For the moment I use the latest PellesC tools on 4.60Beta3 also)

/Edit:
I will update also to the LATEST msvcrt.lib after release of PB
Reason is here:
http://www.purebasic.fr/english/viewtop ... 12&t=46361