[shell-coding] Re: howto talk to lsapi.dll (or any other dll)?



It may not be new, but it was internal before, at least in another form, by exposing it in that api though, you are locking LiteStep into that format; it will either have to be maintained or depreciated. The insane hacks that keep getting added to LiteStep are only hindering it.


What in the world are you talking about?!


Perhaps what is needed is better design, something a little more thought out. I can speak from experience when working on Phoenix that all these neat little hacks and additions are a pain in the ass to support later if you want to do anything besides what is already being done.


Phoenix was the worst hack of LS I've ever seen. I'm thrilled
to see it dead.


If this mailing list is to discuss shell features and coding, perhaps a better solution would be to hash out an alternative system instead of just releasing a new api that might not be supported by every LiteStep build.

Just my two cents, I think any major additions to the api should be ratified by the majority of code and module developers; perhaps there is a better way, or the functionality isnt needed at all.



A bureaucracy! That'll fix everything!
=P

--
Maduin



__________________________________________________
Subscription options and archive:
http://www.freelists.org/list/shell-coding

Other related posts: