Re: my $.02

new topic     » goto parent     » topic index » view thread      » older message » newer message

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>&nbsp;</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>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>I have to throw mine in too...</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; 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>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>*dumb suggestion ahead*</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>&nbsp;&nbsp;&nbsp; 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>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2><FONT face=Arial size=2>*end dumb 
  suggestion*</FONT></FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>Hi Jason:</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>It's not a "dumb suggestion", but there seem to 
  be a&nbsp;few questions that </FONT></DIV>
  <DIV><FONT face=Arial size=2>need to be answered: </FONT></DIV>
  <DIV>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>1.Who will create and maintian this second set of
  includes?&nbsp;People barely have&nbsp;</FONT></DIV>
  <DIV><FONT face=Arial size=2>time to contribute things as it is.</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>2.Who will decide what this second&nbsp;set is 
  to&nbsp;contain, and when should&nbsp;changes </FONT></DIV>
  <DIV><FONT face=Arial size=2>be allowed?</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>3.&nbsp;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>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>4. How is this supposed to help&nbsp;those 
  programmers who write all their own&nbsp;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>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>Regards,</FONT></DIV>

--Boundary_(ID_EsHwQ9SvsFROfWNx35T+NA)--

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu