PureBasic Forums - English

Ok, it looks like some bug has been fixed or something XD, with Paul's help. Could you update your TB and tell me if you still have problems?

Thanks a lot for you help and bug reports. Regards,

El_Choni wrote:Ok, it looks like some bug has been fixed or something XD, with Paul's help. Could you update your TB and tell me if you still have problems?

Thanks a lot for you help and bug reports. Regards,

Thank Paul & El..

- np

Bug found: Paths with a space symbol within are broken.

Here is a procedure for it: Please repair, I want to generate my libs .

I ll check this when I m back, thanks. Regards,

Works great over here..
Thats the lib..

and here's a working example, compiled as Console App ..
drop to command line and feed it some params..

Maybe you forgot to make it ProcedureDLL.s ?

- np

Quick question.. If I create a lib with 50 functions.. and I only use one
function.. do the other 49 get added to my exe?

Or should I play it safe and make one lib for every function?

- np

Only the used function (and the global variables it uses) will be included with the exe.

Regards,

From the help:

MORE IMPORTANT: Using the following prefixes for library or function names may induce TailBite to unexpected errors: "PB_", "_PB", "p_", "v_", "e_", "t_", "a_", "_S", "l_", "s_". I strongly recommend you to avoid using such prefixes, specially the first two.

This can also jack up on anything ending with one of those, eg "ra_" or "rv_".

How big a job to change this so that the alphabet is not so, um, used up. Eg, including the letters "TB" to make "TBa_".

Pretty low priority BTW, just think it would be neater.

(Shouldn't be to hard for the AI king )

Edit:
To clarify the "ending with one of these" I meant the prefix ended with, eg, ra_mySomething. rv_* and ra_* caused polink external not found errors.

Donno, all of my current libraries have MINI_, SC_ and HIB_ prefixes So those prefixes are mine

Another question:

How hard would it be to have Tailbite check for a commented "TailBite Directive". For example:

;TAILBITE IGNORE_FOLLOWING
;TAILBITE INCLUDE_FOLLOWING

To turn off and turn on again code that TailBite uses?

hehe. Users - don't you love them.

why not just use CompilerIf and CompilerEndIf ?

freak wrote:why not just use CompilerIf and CompilerEndIf ?

Yep. Could also have two container progs that just xIncludeBinary.

Was just a lazy man's thought . With a commented directive you wouldn't need to modify code.

Eg, with a DLL and a LIB, you either pull out the procedureDLL attachprocess or flag set and compilerif for each process (compile DLL or make lib).

If the TailBite directive was there, no need to touch it, or have two things to mod.

I'll check it, thx. Regards,

Hmm.. having lots of issues.

- np

Yet they compile ok as DLL..

NoahPhense wrote:Works great over here..

Code: Select all

ProcedureDLL.s ProgramParameters() 
  Char.s = ProgramParameter() 
  While Char.s <> "" 
    Param.s + Char.s + " " 
    Char.s = ProgramParameter() 
  Wend 
  ProcedureReturn Left(Param, Len(Param)-1) 
EndProcedure 

Thats the lib..

and here's a working example, compiled as Console App ..

Code: Select all

MessageBox_(0, ProgramParameters(), "test", 0)
End

drop to command line and feed it some params..

Maybe you forgot to make it ProcedureDLL.s ?

- np

Well, you don't understand me! It isn't a bug of my lib, I don't want to create a lib, but when I want to compile a lib in the Path C:\Dokumente und Einstellungen\... The lib is called Dokumente, because Tailbite tailbites just the File, which seems to be the first parameter. The ProgramParameter cuts the first param with a ending of one space, so Tailbite wants to compile C:\Dokumente and not C:\Dokumente und Einstellungen\... because C:\Dokumente is the first parameter.
Well, that was a help for El_Choni, so he shouldn't use just ProgramParameter() but my ProgramParameters() function.


So El_Choni: the newest version of Tailbite compiles all, but the Libraries doesn't work anymore. Can you give me the TB 1.2 Beta 1.2 ?