TheSwamp
Code Red => AutoLISP (Vanilla / Visual) => Topic started by: d2010 on September 22, 2022, 05:45:13 AM
-
Hi.
I have this my problem.
The visual lisp inserts too many the copyrightAuthorViolations on large scale
on web, inside .vlx.
Eg.1 The team (c) of BorlandDelphi keep the copyright message inside .dll.
Eg.1 If I compile the Cohertal.dll ,then you see this picture-bellow.
How to avoid too many copyright-violation/s when anyone sell the programVlx on the Market-place?>
I hope you undertand me; I do not tell you about "violations with crack.exe,
not license not updated, not Hdd-backup to others computers, not false-serial
numbers generated automatic for user-registered .
:sniffles:
i tell you about violation/s of source/s (lisp+ascii or binary+.fas),
after the Hacker steal your .fas-program.
In my mind, the program "pp_releveu_ferestre.fas" become a source, after
my friend re-use the "pp_releveu_ferestre.fas" inside his program.vlx.
-
just because it has a copyright doesn't mean you can use it.
// Permission to use, copy, modify, and distribute this software in
// object code form for any purpose and without fee is hereby granted
-
just because it has a copyright doesn't mean you can use it.
// Permission to use, copy, modify, and distribute this software in
// object code form for any purpose and without fee is hereby granted
How we,to control the future-of- used?
We need the control the future of our source Lisp, even .fas?
Did Java Authors of source.java, control (check) the future of his Java-applet(=.jar)?
We need checking, the evolution of our program/s in the Market?
(subject "of program/s in "=program lisp-ascii, or C#.dll, .fas or vlx.C#.exe)
-
i use this to protect my app :mrgreen: