Open vlx file

Is there currently anything on the market that will open a vlx file? I ask because I want to convert some of my .lsp files over to .vlx for protection. Thanks much.

 

Not that I've ever heard of...all my LISP routines are kept safe at my house with only the vlx's here at work...job security my friend...lol

 

You can also protect your lsp routines with Kelvinator. Want it?

 

Not that I've ever heard of...

Sure? Let me to doubt of it.
Somebody wants to try?
Just send to me your FAS or VLX application.

 

So finally is all working now?... what is going to be the use for this?...

Its really works for about 95% compiled LISPs. But I have no plans now.
I thought of opening of the service on restoration of the lost sources.

WBR, Eugene

 

Anyone can write a lisp compiler. Here is how

Make you tuff algorithm first.



Say

a= Format$(Asc("A"), "@" & String(Left(Asc("A"), 1), " "))

(this sample is very dummy don't use it)



Then with an external function you convert your lisp and load it in fly
(during a drawing session start from 1 or 2 simple lisp). For your security
you can have some protection set either in your lisps to make sure they are
not modified etc.



It is a little complicated thing but fully possible.

 

D2H, I realize you're speaking lightly, and I don't want to sound accusatory, but depending on the circumstances, your employer might actually have a valid claim to owning your source files.

Copyright issues can be complex, and you might want to consider your "exit strategy" if you were to leave that job under different scenarios. At best, I'd guess that your employer would be very unhappy to discover that they were depending on programs that they couldn't maintain or modify in the future, even if you were legally in the right. Assuming you're on good terms with them now, it might be wise to discuss these things hypothetically and write up an agreement on who gets what if you leave, if only to avoid hard feelings or repercussions down the road.

I compile my lisps at work for several reasons, one being that I can add some "security" features to ensure that they won't run outside the context of our office-standard CAD setup. This was in response to a situation where a bunch of our lisps walked out with an employee who left us. As a matter of pride, if nothing else, I don't want a competing firm to have the free benefit of my hard work. My security tweaks would be pretty easy to overcome by a decent lisper with access to the source code, but they're reasonably bulletproof once compiled.

I keep my source files in a network folder which only me and my boss can access, and I've included enough documentation for someone else to understand how it all works. I don't want the company to be immobilized if I were unexpectedly incapacitated. Our understanding, needless to say, is that they own the copyright to the programs I create as part of my job, but I'm entitled to keep a personal copy of "my" code for reference, as long as I don't transmit it as is to another firm. This is based on our having a good relationship and mutual trust.

Just a few thoughts, no offense intended.