1. my $.02
This is a multi-part message in MIME format.
------=_NextPart_000_0047_01C10003.615BE9C0
charset="iso-8859-1"
I have to throw mine in too...
I have to say that I disagree that a namespace fix should be added =
to the interpreter. If any change is made, I (personally) think it =
should be in the way the Euphoria community "works together", if there =
is such a thing in this day and age.
*dumb suggestion ahead*
What if, to help reduce the number of namespace conflicts, there =
were a set of includes that could be downloaded as an alternative to the =
standard set, in whole or in part. With some patience and time, I =
believe that such a set could grow into a very useful set of libraries =
if additions were made carefully.
*end dumb suggestion*
If the "euphoria community" began to work together in such a =
venture, it would not break any code. As a matter of fact, I think any =
libraries added to the set would naturally have to have a minimal number =
of globals declared, just to be compatable with current/future additions =
or versions, thus reducing the number of namespace conflicts anyway.
This one-minded approach would be much more friendly to newbies, who =
would not really have to worry about what's compatable with what (as =
long as it's from the set), or what do they need to modify, leaving them =
to worry more about what they want to make with it.
I guess the point of all this is; if everyone uses a "base-set" of =
libraries, or files *from* the base set, and then builds on it as =
required by their program, we wouldn't have to worry as much about how =
to solve the namespace problem, only about how to add to what we have to =
make it all better.
Just my 2-cents,
Jason
------=_NextPart_000_0047_01C10003.615BE9C0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I have to throw mine in =
too...</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2> I have to say that I =
disagree=20
that a namespace fix should be added to the interpreter. If any change =
is made,=20
I (personally) think it should be in the way the Euphoria community =
"works=20
together", if there is such a thing in this day and age.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>*dumb suggestion ahead*</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2> What if, to help =
reduce the=20
number of namespace conflicts, there were a set of includes that could =
be=20
downloaded as an alternative to the standard set, in whole or in part. =
With some=20
patience and time, I believe that such a set could grow into a very =
useful set=20
of libraries if additions were made carefully.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2><FONT face=3DArial size=3D2>*end dumb=20
suggestion*</FONT></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2> If the "euphoria =
community"=20
began to work together in such a venture, it would not break any code. =
As a=20
matter of fact, I think any libraries added to the set would naturally =
have to=20
have a minimal number of globals declared, just to be compatable with=20
current/future additions or versions, thus reducing the number of =
namespace=20
conflicts anyway.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> This one-minded =
approach would=20
be much more friendly to newbies, who would not really have to worry =
about=20
what's compatable with what (as long as it's from the set), or what do =
they need=20
to modify, leaving them to worry more about what they want to make with=20
it.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2> I guess the point of =
all this=20
is; if everyone uses a "base-set" of libraries, or files *from* the base =
set,=20
and then builds on it as required by their program, we wouldn't have to =
worry as=20
much about how to solve the namespace problem, only about how to add to =
what we=20
have to make it all better.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2> Just my =
2-cents,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> =20
Jason</FONT></DIV>
------=_NextPart_000_0047_01C10003.615BE9C0--
2. Re: my $.02
This is a multi-part message in MIME format.
--Boundary_(ID_EsHwQ9SvsFROfWNx35T+NA)
----- Original Message -----
From: Jason
I have to throw mine in too...
I have to say that I disagree that a namespace fix should be added to the
interpreter. If any change is made, I (personally) think it should be in the way
the Euphoria community "works together", if there is such a thing in this day and
age.
*dumb suggestion ahead*
What if, to help reduce the number of namespace conflicts, there were a
set of includes that could be downloaded as an alternative to the standard set,
in whole or in part. With some patience and time, I believe that such a set could
grow into a very useful set of libraries if additions were made carefully.
*end dumb suggestion*
Hi Jason:
It's not a "dumb suggestion", but there seem to be a few questions that
need to be answered:
1.Who will create and maintian this second set of includes? People barely have
time to contribute things as it is.
2.Who will decide what this second set is to contain, and when should changes
be allowed?
3. If there were a set of "authorized includes", would that tend
to discourage people from trying to come up with something "better"?
4. How is this supposed to help those programmers who write all their own
code,
but still need badly need namespacing? From my count, those who have been
the heaviest contributors to the namespace debate are the same ones who
are writing or maintaining large programs.
Regards,
Irv
--Boundary_(ID_EsHwQ9SvsFROfWNx35T+NA)
Content-type: text/html; charset=iso-8859-1
Content-transfer-encoding: 7BIT
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="MSHTML 5.00.2614.3500" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV> </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px;
PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A href="mailto:mirwalds at swbell.net" title=mirwalds at swbell.net>Jason</A>
</DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>I have to throw mine in too...</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2> I have to say that I disagree
that a namespace fix should be added to the interpreter. If any change is
made, I (personally) think it should be in the way the Euphoria community
"works together", if there is such a thing in this day and age.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>*dumb suggestion ahead*</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2> What if, to help reduce the
number of namespace conflicts, there were a set of includes that could be
downloaded as an alternative to the standard set, in whole or in part. With
some patience and time, I believe that such a set could grow into a very
useful set of libraries if additions were made carefully.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2><FONT face=Arial size=2>*end dumb
suggestion*</FONT></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>Hi Jason:</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>It's not a "dumb suggestion", but there seem to
be a few questions that </FONT></DIV>
<DIV><FONT face=Arial size=2>need to be answered: </FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>1.Who will create and maintian this second set of
includes? People barely have </FONT></DIV>
<DIV><FONT face=Arial size=2>time to contribute things as it is.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>2.Who will decide what this second set is
to contain, and when should changes </FONT></DIV>
<DIV><FONT face=Arial size=2>be allowed?</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>3. If there were a set of "authorized
includes", would that tend </FONT></DIV>
<DIV><FONT face=Arial size=2>to discourage people from trying to come up with
something "better"?</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>4. How is this supposed to help those
programmers who write all their own code,</FONT></DIV>
<DIV><FONT face=Arial size=2>but still need badly need namespacing? From my
count, those who have been </FONT></DIV>
<DIV><FONT face=Arial size=2>the heaviest contributors to the namespace debate
are the same ones who </FONT></DIV>
<DIV><FONT face=Arial size=2>are writing or maintaining large
programs.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>Regards,</FONT></DIV>
--Boundary_(ID_EsHwQ9SvsFROfWNx35T+NA)--
