Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!.POSTED!not-for-mail From: Jan Burse Newsgroups: comp.lang.java.programmer Subject: Re: Fav. Memory Stream Impl. Date: Wed, 08 Feb 2012 20:23:17 +0100 Organization: albasani.net Lines: 48 Message-ID: References: <4ed0101b$0$282$14726298@news.sunsite.dk> <9jflnkFnrgU1@mid.individual.net> <9jgqmvFjc4U1@mid.individual.net> <6b19df45-6141-45f0-ae2e-8ff30ece4928@y42g2000yqh.googlegroups.com> <9ji3juFomgU1@mid.individual.net> <4f308742$0$282$14726298@news.sunsite.dk> <4f31d7a2$0$293$14726298@news.sunsite.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: news.albasani.net kQLqsrrXwmLel6xxGqwMe2ftuLvo8Uq9UExx8vOky8kabXSvOREHS2H+3waLdbgKSL5fazoFPBh82mSuV11ELlOCQChZo6ZTQH9cU7YTUqV44ztojyeoAQkhE5U0vLit NNTP-Posting-Date: Wed, 8 Feb 2012 19:23:17 +0000 (UTC) Injection-Info: news.albasani.net; logging-data="eec5pO/tYccTkqWMjNNbMUk4gGAghMaLJsn8gELhq3g3Yi2xnS+TRrE1q/kGYnq4/egidVf7rVKzrlZ2+LFxwVti64IyjDn+Z+L24tRvsBDDvHp5ijiIQfySrX68MUse"; mail-complaints-to="abuse@albasani.net" User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0) Gecko/20120129 Firefox/10.0 SeaMonkey/2.7 In-Reply-To: Cancel-Lock: sha1:6Z1FzoaYHVdnspF9tCGQl+KZzpQ= Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:11857 John B. Matthews schrieb: > In article, > Jan Burse wrote: > >> Well with your attitude you would not be >> fit to implement against a specfication. > > Some specifications are better than others: > > > > Thank you for reminding me how much I value the critical feedback of my > colleagues and my manager's diligence in fostering peer review. I shall > bring baked goods to my next meeting. > The cookies will not make the people who should understand or feedback on the spec more intelligent. See what happended in this thread. I wrote: On 11/26/2011 6:10 AM, Jan Burse wrote: > I am not looking for a bounded memory stream, it > should be unbounded, like (temporary) files are. > You just write and write and write, thats it. > > Size control of the memory stream can be done > via close truncate for example. Then this clever guy who will never be able to code or suggest solutions wrote: On 02/07/2012 2:59 AM, Arne Vajhøj: > Given that memory/available address space is > bounded then what you can store in memory will > be bounded no matter what. > > You will just need to code to handle it. Was this a reminder from theoretical computer science that we deal with finite machines, or what? Thats new to me. (no) Looks smart, but is just this relentless stupid asking and commenting that would allow to expell any person in some peer reviewer postion from the team for fooling around and not working. Bye