forums.silverfrost.com

[KennyT]

hi,

i'm in the middle of trying to port to 64 bit and find that certain commands in my .SLK scripts aren't supported in the new .LNK ones, specifically:

debug
insert

the first one may not be important but the lack of the second one is going to cause me some issues with trying to maintain compatibility between the two platforms.

Are the any plans to add an "insert" command or is there an easy workaround/alternative?

K

[PaulLaidler]

Kenny

"Insert" appears to be an undocumented SLINK command. You may be the only user that knows about it. All that I can do is to add it to the wish list for SLINK64.

I can't think of an easy workaround other than the obvious "find and replace" in a text editor.

[StamK]

Wanted to update that now the "insert" command in slk files does work in 64bit, BUT only if there are no empty lines.

Somehow if it finds an empty line it thinks that it is the end of file.
so if you load an slk file as below via an insert command:

lo file1.obj

lo file2.obj

it will only load file1.obj in 64bit (fine in 32bit).

[StamK]

Also forgot to mention that in 64bit only one level of nesting is allowed, so if you use "insert" to call an slk file which has another "insert" command, it will fail (fine in 32bit).The error is

***Only one level of 'insert' permitted

[PaulLaidler]

Thanks for the information. I hope that you can find a way around these limitations.

[StamK]

It's called Copy and Paste, and Delete. But obviously a minor (but annoying) bug in the grand scheme of things. Thanks

[PaulLaidler]

Sorry if it is annoying. SLINK "insert" is an undocumented feature that I did not know about and may have been provided specifically for your company.

SLINK64 is a completely new product so any missing features may be annoying but they are not bugs.

I hope that the basic SLINK64 "insert" command that I have added for you is a step in the right direction.