Page 1 of 3

Compile a PB into PB library

Posted: Sun Mar 11, 2007 5:06 pm
by SkyManager
It would be nice to compile PB procedures into a standard PB library so that programmer can easily build up their own library for fast application programming.

I know that we can use ASM or C/C++ to do that.
But this is a very funny logic : I thought most PB users hate coding in ASM or C/C++ and that they choose to use Basic. If PB users are good at ASM or C/C++, they will simply use C/C++ and they will forget PB.

I do not want to use third party library such as Tailbite!

Re: Compile a PB into PB library

Posted: Sun Mar 11, 2007 7:25 pm
by Kale
SkyManager wrote:I do not want to use third party library such as Tailbite!
Why not? as this allows you to do exactly this. :shock:

Posted: Sun Mar 11, 2007 8:27 pm
by Hroudtwolf
@SkyManager

Good idea.
I agree with you.

It would be very cool to have such a compiler feature(option).

Re: Compile a PB into PB library

Posted: Sun Mar 11, 2007 9:30 pm
by PB
> Why not?

Tailbite is too hard to set up (I got too many errors to bother with it).
Also there is no guarantee of future versions if the author gives up on it.
A native PureBasic "Create library" menu command is just so much easier.

Posted: Sun Mar 11, 2007 10:06 pm
by SCRJ
Agree, would be a nice feature. :D

Posted: Sun Mar 11, 2007 10:39 pm
by Kaeru Gaman
yep, would be fine.

Posted: Mon Mar 12, 2007 10:08 am
by Derek
Would be handy to have it built in.

Posted: Mon Mar 12, 2007 10:11 am
by Hydrate
I couldnt agree more, this would be very usefull.

For now we can all just make dll files and give people the information though no? lol.

Posted: Mon Mar 12, 2007 11:04 am
by SkyManager
If Tailbite can do it, I'm sure PB can do it too.

For the PB team, please read this
If PB users are good at ASM or C/C++, they will simply use C/C++ and they will forget PB.

Posted: Mon Mar 12, 2007 11:15 am
by traumatic
SkyManager wrote:For the PB team, please read this
If PB users are good at ASM or C/C++, they will simply use C/C++ and they will forget PB.
Repeating a phrase doesn't necessariliy make it true. ;)

Posted: Mon Mar 12, 2007 7:01 pm
by DarkDragon
You want to wait longer and longer for your PB updates?! Bad decision and bad way of adding features. My feature wish would be a second and a third Fred: then they can manage such a lot parts of PureBasic maybe.

Posted: Mon Mar 12, 2007 7:04 pm
by Killswitch
El_Choni is Tailbite's author, so he's clearly capable of implimenting this feature - why not let him create a version that can be built into the PB compiler? I'm sure niether party would begrudge a small fee :)

Posted: Mon Mar 12, 2007 7:44 pm
by Denis
I Agree with you SkyManager.

Tailbite was done because such a tool was lacking.
I think it's time to add this.

Posted: Mon Mar 12, 2007 8:03 pm
by netmaestro
El_Choni wrote:I haven't had time for coding at all lately, and I doubt I'll have any in the future.
As sad an eventuality as this is, we must face the fact that Tailbite's future development will have to continue without the participation of the original author. I hope the PureBasic team will see fit to take it on and bring it under the Fantaisie umbrella, but in the end it's entirely up to them to decide whether that's something they want to do.

Speaking only for myself, I can say without reservation that I'd be glad to pay for a library compiler as an add-on product to PureBasic, and I'm sure I'm not alone in this view.

To El_Choni: Thank you very much for creating and supporting this tool over the past years. It truly is a fine piece of work and much appreciated by a great many PureBasic coders. I wish you all the very best in the future.

Posted: Mon Mar 12, 2007 10:26 pm
by srod
With PB4 of course we find that using the threadsafe switch causes different versions of certain library routines to be linked in with the final executable. Consequently, we find ourselves having to create multiple versions of our tailbitten libs just to cater for the different switches. Of course, it is possible to create one tailbitten lib which caters for ansi/unicode/threadsafe etc. but this does involve a little more work for the creator of the lib.

I just prefer to use source code include files and that way remain completely in control.

In a way I wish PB generated threadsafe code without exception, at least this way we wouldn't have to worry about the different library versions. Dito for Unicode. Sure it might slow some routines down a little, but hey there's always inline asm etc.