From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,36a29c2860aff686 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII Path: g2news2.google.com!postnews.google.com!21g2000prv.googlegroups.com!not-for-mail From: Shark8 Newsgroups: comp.lang.ada Subject: Re: Properties Date: Mon, 6 Dec 2010 15:22:22 -0800 (PST) Organization: http://groups.google.com Message-ID: <923f0664-890d-4ca9-9b34-2da64067b068@21g2000prv.googlegroups.com> References: <3b84c8e7-1a51-4a7c-9646-119f1fc51478@s4g2000yql.googlegroups.com> <4pnv7nl4cdui$.1n28i7lqk4mek$.dlg@40tude.net> <1k7367gtebsgm$.18auo6u3nfg34.dlg@40tude.net> <618677c8-a44f-443e-9052-a94fb48c999a@s4g2000yql.googlegroups.com> <066181c0-9b80-4c17-a7b4-7ef28a297ea4@e16g2000pri.googlegroups.com> NNTP-Posting-Host: 174.28.191.40 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1291677742 29008 127.0.0.1 (6 Dec 2010 23:22:22 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Mon, 6 Dec 2010 23:22:22 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: 21g2000prv.googlegroups.com; posting-host=174.28.191.40; posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12 ( .NET CLR 3.5.30729; .NET4.0E),gzip(gfe) Xref: g2news2.google.com comp.lang.ada:16796 Date: 2010-12-06T15:22:22-08:00 List-Id: > > I defiantly agree with the Hungarian notation. > > followed by > > The type declaration carrys the type information. It does NOT > belong in the name (of the variable). =A0It creates a =A0 > maintenance nightmare also -- change the type and all > instances of the name must be changed. =A0 > > BLECH. Eh, my mistake, I meant to say "I defiantly agree with you on the Hungarian notation." > > I agree with you about the WORD, DWORD, pointer thing. It > > would be better to have actual types with actual > > parameters/fields... > > Yes. Every event and API is usually specific enough for real > type definitions. > > > but then the same could be said about > > the 'typless' FSes for *nix and windows > > That is something different. A "file" is a perfectly generic > container of information. Do you want to allow your software > to decide the format? Or would you prefer the OS to do it > instead? =A0Something must decide. Er, I think you misunderstand what I mean by "typed files" very often "the software" does NOT & should NOT decide the format; if that were the case then "the software" could say "my HTML file writer doesn't need ending tags!" or "I don't need to write the header for an .ICO file!" which misses the whole point of having a specified standard. IOW, the type of a file, having some definition, SHOULD ensure that the file has the correct layout... like Access ensures that our "pointer" *IS* to a variable of the specified type. > Prior to Unix, everything was a unit record of some sort. It > still is on the non-UNIX (non-hierarchical) parts of a > mainframe: > > //DATAOUT DD DSN=3DM0DXYZ.DATA, =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 > // =A0 =A0 =A0 =A0 =A0 DISP=3D(NEW,CATLG,DELETE), =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 > // =A0 =A0 =A0 =A0 =A0 SPACE=3D(TRK,(10,10),RLSE), =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 > // =A0 =A0 =A0 =A0 =A0 DCB=3D(RECFM=3DFB,LRECL=3D23,BUFNO=3D10,OPTCD=3DC) > > Do you want to go back to specifying all these file > attributes? RECFM=3D? LRECL=3D? BLKSIZE=3D? bLECH. Not to > mention it complicates ftp transfers etc. : > > LOCSITE LRECL=3D80 RECFM=3DFB BLOCKSIZE=3D320 CYLINDERS \ > =A0 PRIMARY=3D2 SECONDARY=3D2 > > Blexhch. It actually makes a lot of sense to be able to have some sort of "unit record" in files, especially if you are dealing with databases and, in that case, units should be able to be individually locked. As for specifying all the little attributes of some file, why not treat it the same way I do in Ada: unless there is some specific reason to do otherwise [like hardware interfacing] let the compiler choose the attributes of the type like 'Size, 'Bit_Order? > > One of the best things about Unix is that it finally tossed > aside all of these silly hinderances. =A0Everything since has > copied this thinking. Just because everything copies the thinking neither means that the thinking is correct or useful. (Though it doesn't mean that it's wrong or useless either.)