You only have to say it once -- if you get it right. This you have yet to do. 'Environment' has too many different meanings, all of which make sense in this context, few, if any justify your assertions, none your impatience.
On Mar 1, 9:25 am, Shane Isbell <shane.isb...@gmail.com> wrote: > On Tue, Mar 1, 2011 at 9:15 AM, Indicator Veritatis <mej1...@yahoo.com>wrote: > > > > > > > > > > > The way you reach your conclusion from your premises is so illogical, > > you are casting doubt on your own ability to think logically enough to > > be a competent programmer. > > > The real reason Dianne has "quite a following" is because she really > > does know Android extremely well, having been at the center of > > everything Android since very near its beginning. And she has > > dispensed a great deal of valuable Android knowledge in this forum > > over the years, too, even if some of her responses were so brief they > > read like Delphic utterances:( > > > And not surprisingly, Dianne is 100% correct on this one: hard coding > > package names is bound to break the code, whether now or in the > > future. If it really is, as you say, a "hard requirement" then you are > > going to have to resign yourself to having broken code. You have been > > warned, don't shoot the messenger. Go back to your client and explain > > the consequences of this "hard requirement". You just might find it is > > not such a "hard requirement" after all. > > I don't know how many times I have to say but the client has complete > control of the environment. Why is this so difficult to understand? > > Shane -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
