in reply to
Re: Re: Re: Re: Re: Preferred output for development tool
in thread Preferred output for development tool
And now a misquote!
The actual quote is "Castaway told me that if I documented it properly (forgot her exact words)..." HER words, not mine.
Over documenting just in case there is a big change in plans for the script shouldn't be considered a good thing. You could write 10 lines of comments for every line. That might help in some cases, but it will return a net loss if your projects tend to be well planned. I had an idea, and it was alot easier to alter the script I had than to start from scratch with a full "plan" on the best way to develop the code from beginning to end. Sometimes being ill prepared is unavoidable.
EDIT.... I better defend LinkStructor too, since that involves money. You said
"The most concerning thing in all this is that the LinkStructor program in question, you are intending to market for your own commercial gain. This, despite acknowledged security holes and bugs.
Yes, I admit there is a bug in a feature of LinkStructor that isn't turned on for the demo (which is still available upon request). That's what development is all about. There is no fee yet, and it runs on my home computer only. I'm not aware of any security holes, but not going to assume there aren't and I want to oversee its use for now. There was a possibility that requests would become unreadable, but even that might no longer be an issue.