[M3devel] quick question for the Modula-3 ether... LONGFLOAT??
Jay
jay.krell at cornell.edu
Mon Apr 13 02:00:40 CEST 2009
Here is the stuff I was talking about:
http://modula3.elegosoft.com/cgi-bin/cvsweb.cgi/cm3/m3-libs/m3core/src/float/Common/
This stuff is "standard" and in the green book.
Surprising that both names occur here, float and real.
You can see your example sort of proves my point.
Imagine if there was no case sensitivity.
Or if you aren't keen on identifiers varying only in case.
The below needs to setup a parallel set of names for "wrapper types", or WrapperModule.T.
Changing "Float" to "Real" or vice versa can help.
Though, now that I'm saying it, it feels a bit sleazy.
Maybe better to invent a prefix or suffix.
IntegerValue, RealValue, etc.
(That reminds me, I've seen "reel" used in a similar fashion.)
You know, using homonyms -- ea vs. ee, y for long i, etc.
tipe, type
runtime, runtyme
- Jay
> To: jay.krell at cornell.edu
> Date: Sun, 12 Apr 2009 15:22:23 -0700
> From: mika at async.caltech.edu
> CC: m3devel at elegosoft.com
> Subject: Re: [M3devel] quick question for the Modula-3 ether... LONGFLOAT??
>
>
> It seems a bit more common a term than I would have thought from
> someone's making a mistake.
>
> I am talking about things like this. In the stubgen sources, there are
> two interfaces: Value.i3 and Type.i3.
>
> Not the only place I've seen it in Modula-3.
>
> Value.i3 has:
>
> TYPE
> T <: ROOT;
> (* Ordinal | Float | LongFloat | Extended | ArrayOrRecord | Set |
> Text | Null *)
>
> Ordinal = T OBJECT ord: INTEGER END;
> (* ORD(the value) *)
>
> Float = T OBJECT val: REAL END; (* XXX *)
>
> LongFloat = T OBJECT val: LONGREAL END; (* XXX *)
>
> Extended = T OBJECT val: EXTENDED END;
>
> ...
>
> Type.i3 has:
>
> TYPE
> T <: OBJECT name: Qid; visited := FALSE; brandsOK := TRUE END;
>
> (* Ordinal | Real | LongReal | Extended | Reference | Array
> | Packed | Record | Set | Procedure *)
>
> Ordinal = T BRANDED OBJECT END; (* Enumeration | Subrange *)
>
> (* ... *)
>
> Real = T BRANDED OBJECT END; (* YYY *)
>
> LongReal = T BRANDED OBJECT END; (* YYY *)
>
> Extended = T BRANDED OBJECT END;
>
> ...
>
> Is there a reason or is this just inconsistent crud from before the
> glaciers came thru?
>
> Mika
>
>
> Jay writes:
> >--_eaf98d33-2bbc-4e5b-8afc-bc1f32079c51_
> >Content-Type: text/plain; charset="iso-8859-1"
> >Content-Transfer-Encoding: quoted-printable
> >
> >
> >1) I'm sure it is a natural term to all the other programmers=2C easy mista=
> >ke to make.
> >
> >=20
> >
> >2) There in fact this natural need to come up with alternate names.
> >
> >You know=2C if you read the compiler and runtime source=2C you see things c=
> >alled Type and/or Tipe=2C not just Type=2C because Type (or at least TYPE) =
> >is already a reserved word if you write "metacode" dealing with types=2C yo=
> >u can't use that name.
> >
> >=20
> >
> >In that vein there are some public m3core modules for dealing with floats/r=
> >eals/whatever and they might use names like this.
> >
> >=20
> >
> > - Jay
> >
> >
> >=20
> >> To: m3devel at elegosoft.com
> >> Date: Sun=2C 12 Apr 2009 13:05:49 -0700
> >> From: mika at async.caltech.edu
> >> Subject: [M3devel] quick question for the Modula-3 ether... LONGFLOAT??
> >>=20
> >>=20
> >> Does anyone out there have any idea why a lot of bits of Modula-3
> >> refer to something called "LONGFLOAT" or "LongFloat". I just checked
> >> Wirth=2C and Modula-2 used "REAL" as well so it doesn't seem like
> >> LONGREAL would ever have been called "LONGFLOAT".
> >>=20
> >> Is LONGFLOAT/LongFloat of any significance or is it OK to
> >> search-and-replace it away with LONGREAL/LongReal everywhere?
> >>=20
> >> (I'm talking about things like the emacs macro package as well as
> >> all over m3tk...)
> >>=20
> >> Mika
> >
> >--_eaf98d33-2bbc-4e5b-8afc-bc1f32079c51_
> >Content-Type: text/html; charset="iso-8859-1"
> >Content-Transfer-Encoding: quoted-printable
> >
> ><html>
> ><head>
> ><style>
> >.hmmessage P
> >{
> >margin:0px=3B
> >padding:0px
> >}
> >body.hmmessage
> >{
> >font-size: 10pt=3B
> >font-family:Verdana
> >}
> ></style>
> ></head>
> ><body class=3D'hmmessage'>
> >1) I'm sure it is a natural term to all the =3Bother programmers=2C eas=
> >y mistake to make.<BR>
> > =3B<BR>
> >2) There in fact this =3Bnatural need to come up with alternate names.<=
> >BR>
> >You know=2C if you read the compiler =3Band runtime source=2C you see t=
> >hings called Type and/or Tipe=2C not just Type=2C because Type (or at least=
> > TYPE) is already a reserved word if you write =3B"metacode" dealing wi=
> >th types=2C you can't use that name.<BR>
> > =3B<BR>
> >In that =3Bvein there are some =3Bpublic m3core modules for dealing=
> > with floats/reals/whatever and they =3Bmight use names like this.<BR>
> > =3B<BR>
> > =3B- Jay<BR><BR><BR> =3B<BR>>=3B To: m3devel at elegosoft.com<BR>&g=
> >t=3B Date: Sun=2C 12 Apr 2009 13:05:49 -0700<BR>>=3B From: mika at async.cal=
> >tech.edu<BR>>=3B Subject: [M3devel] quick question for the Modula-3 ether=
> >... LONGFLOAT??<BR>>=3B <BR>>=3B <BR>>=3B Does anyone out there have =
> >any idea why a lot of bits of Modula-3<BR>>=3B refer to something called =
> >"LONGFLOAT" or "LongFloat". I just checked<BR>>=3B Wirth=2C and Modula-2 =
> >used "REAL" as well so it doesn't seem like<BR>>=3B LONGREAL would ever h=
> >ave been called "LONGFLOAT".<BR>>=3B <BR>>=3B Is LONGFLOAT/LongFloat of=
> > any significance or is it OK to<BR>>=3B search-and-replace it away with =
> >LONGREAL/LongReal everywhere?<BR>>=3B <BR>>=3B (I'm talking about thing=
> >s like the emacs macro package as well as<BR>>=3B all over m3tk...)<BR>&g=
> >t=3B <BR>>=3B Mika<BR></body>
> ></html>=
> >
> >--_eaf98d33-2bbc-4e5b-8afc-bc1f32079c51_--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20090413/988f071e/attachment-0002.html>
More information about the M3devel
mailing list