Re: Indepth Analyses Of Euphoria Translator
Mike,
> Yeah, but so what?
I've NEVER had a virus infection on any machine for which I was responsible.
> You are saying that not having the source to a
> Euphoria library, can mean that it could be a virus
> and you wouldn't know it, therefore, let us forget
> about DLL compilation and stay in thiss little
> 200-people community with no one knowing we exist, am
> I correct?
No no no. I'm simply saying, should I take the same precautions with DLLs
that I do with EXEs... in regards to their potential use for "bad things."
> Think of customers, people that want to buy plugins
> for apps or games, should they first go to
> www.rapideuphoria.com, download Euphoria To C, visit
> the archive, download the source to your library,
> register Euphoria To C, download a C compiler,
> translate your library to C, link it into a DLL, and
> then use it, just because it *might* contain a virus
> otherwise?
In this case, the DLL would be well-tested and general users could be
reasonably confident that the DLL would perform as specified.
> Just get a Virus Scanner and scan your HD, most email
> clients do that for you automatically anyways, and
> stop worrying!
If I wrote a EUPHORIA program called "FunnyVideo.exe," that actually deleted
all contents off your hard drive, no virus checker is going to be able to
determine what my program does... In this case, it's not a virus, but the
enemy in a trojan horse.
<\<
|
Not Categorized, Please Help
|
|
