Hi Jure

Thank you ! My timeframes have been limited and realised later yesterday
this may be the case, whilst on another job.

Waiting for your confirmation has confirmed it for me.

Grateful to you and other contributors here.

Thank you.

Cheers

Jeremy.

modridirkac <jure.zorko@gmail.com> wrote:
>Yes.
>Now you have in your form (library, script) in uses:
>   uses ObjectPAL
>      "mylib1.lsl", ":APP:lib2.lsl"
>   endUses
>
>You have to change to
>   uses ObjectPAL
>     ; methods in mylib1
>     ChechData(x string, y string) smallint
>     doSomething(x string, var i smallint) logical
>
>     ; methods in lib2
>     xyz() smallint
>     anotherMethod(s smallint) string
>   endUses
>
>
>Most likelly now you have uses ObjectPal "mylib1" endUses
>and then
>   mylib1.ChechData(x)   ; this method does not exist in mylib1 (only one
 
>parameter)
>or some other error/type in calling methods in mylib1.
>Compiler can not find method you try to call.
>Maybe wrong type of parameters, wrong number of parameters, typo in method
 
>name,...
>
>Jure
>
>
>On Tue, 15 Mar 2022 22:56:05 +0100, Jeremy Stagg  
><jeremy.stagg@itsysadmin.com.au> wrote:
>
>>
>> Hi Kevin
>>
>> Clarification requested: "putting all methods needed in the uses block"
>>
>> You are referring to the Uses block within the library and listing its
 
>> methods
>> accordingly in the uses block?
>>
>> Regards
>>
>> Jeremy.
>>
>> "Kevin Zawicki" <numberjack@wi.rr.com> wrote:
>>>
>>> I think you are running into the uses declare the library and not each
 
>>> method
>>> compile issue. I (and others have written quite a bit about this).
>>>
>>> You are better off putting all methods needed in the uses block. It is
 
>>> more
>>> stable and avoids the circular reference.
>>> Also try to have unique method names throughout all forms and libraries.
>>>
>>> Some posts...
>>>
>>> http://pnews.thedbcommunity.com/cgi-bin/dnewsweb?cmd=article&group=pnews.paradox-programming&item=32444&utag=
>>>
>>> http://pnews.thedbcommunity.com/cgi-bin/dnewsweb?cmd=article&group=pnews.paradox-programming&item=38026&utag=
>>>
>>>
>>>
>>> "Jeremy Stagg" <jeremy.stagg@itsysadmin.com.au> wrote:
>>>>
>>>> Having an issue withthe simple delivery of a library (lsl -> ldl) and
 
>>>> the
>>>> resulting compiler warning of:
>>>> "this file does not have any symbol table information".
>>>> This happens when referring to a delivered library from the main form,
>> and
>>>> the library is referred to in the "Uses" list
>>>> of libraries.
>>>> Source library files (lsl) work fine.
>>>> Any tips as there about 1 paragraph I can find that relates to  
>>>> symboltable
>>>> in ObjectPAL, otherwise down a Delphi rabbit hole.
>>>> Cheers
>>>> Jeremy.
>>>
>>
>
>
>-- 
>Using Opera's mail client: http://www.opera.com/mail/