Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

LIBRARY and Pipes

Aug
1,936
71
Since updating to 27.01.22, I am having a problem with LIBRARY functions and piping.

I have my .library files in C:\Program Files\JPSoft\TCMD27\library, so that they are all loaded on startup.

When I run anything through a pipe, all works, except for the warnings;
Code:
e:\utils>dir /[d-0] /od | *view
TCC: The library function already exists "vb"
TCC: The library function already exists "vbtest"
TCC: The library function already exists "AddOne"
TCC: The library function already exists "SVJob"

If I use an in-process pipe, no warnings;
Code:
e:\utils>dir /[d-0] /od |! *view
...and all works as it should.

The reason I am getting those warnings is that I have functions with the same name in different libraries:
Code:
c:\program files\jpsoft\tcmd27\library>ffind /t"vbtest" *.library

---- C:\Program Files\JPSoft\TCMD27\library\calc.library
vbtest {

---- C:\Program Files\JPSoft\TCMD27\library\vb.library
vbtest {

  2 lines in      2 files

As I said, I have only noticed this since updating to 27.01.22

Joe
Code:
     _x64: 1
   _admin: 1
_elevated: 1

TCC  27.01.22 x64   Windows 10 [Version 10.0.19042.928]
 
I have functions with the same name in different libraries:
What does "LIBRARY /F" produce? Do you see more than one with a given name? If all with a given name don't make it into memory, your suggestion (library$command) wouldn't work!
 
Further to my suggestion, it would seem that I had already been using a dot naming convention in my .library files, and had forgotten about it.

After "fixing" the commands to my dot naming convention, library and pipes are working with no warning of duplicate commands in .library files.

Thanks @vefatica for jogging my memory.

Joe
 

Similar threads

Back
Top