for S'Image use Func??
in [ADA]
|
Prev: Question about default discriminants and mutable objects.
Next: Why is not Stream_Access defined Ada.Streams ?
From: Yannick Duchêne (Hibou57) on 11 May 2010 15:03 Le Tue, 11 May 2010 19:05:07 +0200, Warren <ve3wwg(a)gmail.com> a écrit: > As I pointed out earlier, those *printf() arguments are > checked, so it is not strictly untyped. You can lie to > it of course.. Isn't it checked at the compiler option ? Does ANSI or ISO C really requires this ? If so, how is it formalized ? -- pragma Asset ? Is that true ? Waaww... great
From: Maciej Sobczak on 11 May 2010 16:18 On 11 Maj, 16:24, "Dmitry A. Kazakov" <mail...(a)dmitry-kazakov.de> wrote: > > OK, really - what's exactly being inefficient in buffered input? > > You said it, it is buffering. OK, next step: what's exactly being inefficient in buffering in buffered input? > > What I want is a stream interface to the blobs that my filesystem is > > storing for me, so that I can build higher-level constructs on top of > > it. > > But if my file system already has get-line-as-an-array-of-code-points. Why > should I go deeply down to the representation layer, to a stream of octets? Then you shouldn't. The point is that *my* filesystem does not have it (it supports only blobs), so I have a valid use-case for stream of octets. > >> The bottom line is, Ada does it right (tm). > > > If it did it right (tm), I would not have to reinvent > > My_Better.Text_IO. > > You should not. The question was about formatting, I/O is OK. Unfortunately, in Ada the formatting and I/O are entangled in Text_IO. They are "separate" in stream I/O (there is no formatting at all there) and this is what makes stream I/O a valid basis for a custom solution, like My_Better.Text_IO. That's exactly my point. -- Maciej Sobczak * http://www.inspirel.com YAMI4 - Messaging Solution for Distributed Systems http://www.inspirel.com/yami4
From: Maciej Sobczak on 11 May 2010 16:23 On 11 Maj, 17:54, Yannick Duchêne (Hibou57) <yannick_duch...(a)yahoo.fr> wrote: > > (OK, that's enough for off-topic confusions, I duck away to reinvent > > My_Better.Text_IO on top of Ada.Streams ;-) ) > > Please, what does mean to duck away ? The basis is (3rd meaning): http://dictionary.cambridge.org/dictionary/british/duck_3 :-) -- Maciej Sobczak * http://www.inspirel.com YAMI4 - Messaging Solution for Distributed Systems http://www.inspirel.com/yami4
From: Warren on 11 May 2010 16:36 Jeffrey R. Carter expounded in news:cd1877ca-5342-4b1c-9128- f74ebe5da93e(a)o8g2000yqo.googlegroups.com: > So, did you "save" anything? No, you not only didn't save anything, > you wasted your effort by writing and testing code that duplicates > existing functionality, that you were aware of, for no reason. It's my life ;-) Warren
From: Charmed Snark on 11 May 2010 16:50
Dmitry A. Kazakov expounded in news:bpz9dud4c9de.1uloiuk912d7t.dlg(a)40tude.net: > On Tue, 11 May 2010 17:05:07 +0000 (UTC), Warren wrote: >> Empty lines are significant to my parser, > > Then Get_Line is what you have to use. No I don't. Make me.. > BTW, printf is fundamentally uncheckable. Proof: > > char * Format = (HALT (p) ? "%d" : "%s"); > printf (Format, 123); You get what you asked for there, heh heh... I don't ask for such silly things. > Oh, there are so many ways. E.g. > > 1. > type Hex_Dump is new String; > function "&" (Text : Hex_Dump; Value : Integer) return Hex_Dump; Right- you have to "code" it. That's not what I'm talking about. I'm talking about "library support". > I think you've got the idea. You've completely missed the point. > It is also annoying that I cannot output the number's base as > subscript 16. Programming is generally annoying. You completely twist things to keep arguing.. I quit. > I don't say that Ada's formatting is OK. Otherwise I would not write a > formatting library of my own. I just don't consider formatting as an > essential part of the language. Even at the standard library level it > is not. That's an opinion that I don't believe is widely held. But no matter either way, I simply disagree. >>> Nobody want to see fixed font output. >> >> Pardon me? If you give me a report of my >> investment holdings with columns of numbers, >> then those numbers better line in columns as >> well. > > Where is a problem? Fixed point is a relatively > new invention, ... Relatively new? You make me chuckle. I suppose that old ASR33 teletype I had was was ahead of its time with that modern fixed font! Playing star trek on a teletype would have been very interesting in a proportional font. I'm signing off. Warren |