I didn't mean to be so hard but I am just a bit ticked off that my code
inclusion was being stoned without any actual example of why it would need to be
excuded.
This has been happening on this list for a while (I'm talking in general, not
just about my code) and it has started to get on my nerves. It is not
encouraging when the code suggestions being made are being for reasons that are
not applicable.
I have no problem with my code being stoned. "Sticks and Stones etc". But I
would like it to be done in a more specific method. If anyone can come up with
an EXAMPLE (not theory) of why the code should not be changed, then I see no
reason why it should not be included.
I am just getting tired of people jumping to opinions without actually looking
at the code in detail.
Eytan Heidingsfeld wrote:
> For the first time someone agress with me and you stone him? You evil evil
> being!!
> I'm sure he can come up with ideas I'm to busy working right now but since
> (yes me rambling about this again) this is an API we are supposed to do what
> is right and not what is more frequently used.
>
> 8an
>
> _______________________________________________
> Dynapi-Dev mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
--
Michael Pemberton
[EMAIL PROTECTED]
ICQ: 12107010
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
