You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
|
Feb
(5) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(127) |
Oct
(37) |
Nov
(4) |
Dec
(1) |
2002 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
(2) |
Jun
|
Jul
(16) |
Aug
(4) |
Sep
(6) |
Oct
(2) |
Nov
(1) |
Dec
(3) |
2003 |
Jan
(1) |
Feb
(3) |
Mar
(1) |
Apr
(1) |
May
(2) |
Jun
(3) |
Jul
(2) |
Aug
(3) |
Sep
(3) |
Oct
(5) |
Nov
(16) |
Dec
(28) |
2004 |
Jan
(13) |
Feb
(9) |
Mar
(3) |
Apr
(9) |
May
|
Jun
(10) |
Jul
(2) |
Aug
(3) |
Sep
(3) |
Oct
(4) |
Nov
(6) |
Dec
(7) |
2005 |
Jan
|
Feb
(1) |
Mar
(19) |
Apr
(4) |
May
(5) |
Jun
(6) |
Jul
(5) |
Aug
(3) |
Sep
(7) |
Oct
(24) |
Nov
(7) |
Dec
(4) |
2006 |
Jan
(11) |
Feb
(3) |
Mar
(9) |
Apr
(7) |
May
(31) |
Jun
(25) |
Jul
(13) |
Aug
(9) |
Sep
(9) |
Oct
(23) |
Nov
(35) |
Dec
(13) |
2007 |
Jan
(49) |
Feb
(26) |
Mar
(22) |
Apr
(12) |
May
(24) |
Jun
(34) |
Jul
(42) |
Aug
(75) |
Sep
(52) |
Oct
(35) |
Nov
(41) |
Dec
(36) |
2008 |
Jan
(26) |
Feb
(33) |
Mar
(57) |
Apr
(82) |
May
(97) |
Jun
(78) |
Jul
(79) |
Aug
(61) |
Sep
(54) |
Oct
(32) |
Nov
(49) |
Dec
(48) |
2009 |
Jan
(54) |
Feb
(32) |
Mar
(59) |
Apr
(65) |
May
(149) |
Jun
(131) |
Jul
(80) |
Aug
(40) |
Sep
(26) |
Oct
(63) |
Nov
(12) |
Dec
(21) |
2010 |
Jan
(10) |
Feb
(16) |
Mar
(41) |
Apr
(43) |
May
(53) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
From: winnie <don...@ya...> - 2005-11-14 06:44:17
|
Dear Madam/Sirs, see the attached (Lycra + Neoprene Sock) The size : XS,S,M,L, XL and XXL The price is USD4.00/pr Pls give us your feedback if you are interested in our products Thanks, Winnie |
From: Piet P. <pi...@ch...> - 2005-11-10 23:32:35
|
Hi, Quit ov ng for ons - visi aExpre op erpayi your Meddicati t our Pharm ss Sh X V A C V P a A m I I r n L b A A o a I i L G z x U e I R a M n S A c 85,45 99,95 69,95 |
From: Vibeke R. <vib...@th...> - 2005-11-05 16:14:12
|
Goo pa our Meddic it our Phar s Sho d day for you, Quit over ying for y ations - vis maExpres p. AmVIVAXaLeCI bienAGRALIUMnaxvitraALIS 3.301.20 3.70 Read more info - http://procesverbauxndl.demanpla.com |
From: Ikaia S. <sa...@rt...> - 2005-11-04 01:28:23
|
Good d overpayi your Meddica isit our P s Sh ay for you, Quit ng for tions - v harmaExpres op. Submit additional info - http://indigovyb.lowlee.info |
From: David M. <db...@cs...> - 2005-10-31 21:00:12
|
I'm forwarding this digest, edited to remove spam. The items are probably redundant for most of us though. Dave Begin forwarded message: > Resent-From: sml...@li... > From: sml...@li... > Date: October 28, 2005 12:53:04 AM CDT > Resent-To: sml...@li... > To: sml...@li... > Subject: Sml-implementers digest, Vol 1 #236 - 4 msgs > Reply-To: sml...@li... > > > Send Sml-implementers mailing list submissions to > sml...@li... > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/sml-implementers > or, via email, send a message with subject or body 'help' to > sml...@li... > > You can reach the person managing the list at > sml...@li... > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Sml-implementers digest..." > > > Today's Topics: > > 2. new mailing list (Matthias Blume) > 3. Re: [MLton] mutable fields [Re: [Smlnj-dev-list] Evolving > SML] (Henry Cejtin) > 4. Re: [Sml-basis-discuss] new mailing list (Dave Berry) > > > --__--__-- > > Message: 2 > Cc: sml...@cs... > From: Matthias Blume <bl...@tt...> > Date: Wed, 26 Oct 2005 16:45:07 -0500 > To: Peter Sestoft <se...@di...>, > John Reppy <jh...@cs...>, sml...@li..., > po...@po..., sml...@li..., > Martin Elsman <ma...@it...>, Robert Harper <rw...@cs...>, > Andreas Rossberg <ros...@ps...>, ML...@ml..., > Andrew Kennedy <ak...@mi...>, > sml...@cs..., Nick Benton > <ni...@mi...>, > "Claudio V. Russo" <cr...@mi...>, > SML implementers <sml...@li...> > Subject: [Sml-implementers] new mailing list > > We have created a new mailing list for the discussion of > the evolution of SML. The address of the mailing list is: > > sml...@ma... > > Information about the list, including an interface to subscribe, > can be found at: > > http://mailman.cs.uchicago.edu/mailman/listinfo/sml-evolution > > There is also an email-based interface for users of the list; > you can get info about using it by sending a message > with just the word `help' as subject or in the body, to: > > sml...@ma... > > The list is closed, i.e., only subscribers can post messages. If you > have multiple e-mail accounts from which you wish to post messages, > please ask one of the administrators to white-list them. > Alternatively, > you can subscribe multiple times and disable mail delivery for all but > one of your identities. > > The administrators are: > > David MacQueen (db...@cs...) > John Reppy (jh...@cs...) > Matthias Blume (bl...@tt...) > > Kind regards, > Matthias Blume > > > > --__--__-- > > Message: 3 > To: bl...@tt..., se...@di... > Cc: ak...@mi..., cr...@mi..., jh...@cs..., > ma...@it..., ML...@ml..., ni...@mi..., > po...@po..., > ros...@ps..., rw...@cs..., > sml...@cs..., > sml...@li..., > sml...@li..., smlnj-dev- > li...@li... > From: Henry Cejtin <hen...@sb...> > Date: Wed, 26 Oct 2005 20:26:05 -0500 > Subject: [Sml-implementers] Re: [MLton] mutable fields [Re: [Smlnj- > dev-list] Evolving SML] > > I always find it really inelegant that ML has both refs and arrays > instead of > just making one use a vector of refs. I am all in favor of having > compilers > optimize away cases where the refs are not used in a first-class > way, but it > seems to me like a real language wart. Not only that, but it makes > certain > things quite painful which are easy to do in C (like being able to > take the > address of an array element and pass it around to procedures that > are going > to mutate that slot). > > > --__--__-- > > Message: 4 > Date: Thu, 27 Oct 2005 19:53:33 +0100 > To: Matthias Blume <bl...@tt...>,John Reppy <jh...@cs...>, > SML implementers <sml...@li...> > From: Dave Berry <da...@be...> > Subject: [Sml-implementers] Re: [Sml-basis-discuss] new mailing list > > Does this imply that we regard the SML implementers list as dead? > If so, > I'll unsubscribe from it. > > Dave. > > > At 22:45 26/10/2005, Matthias Blume wrote: > >> We have created a new mailing list for the discussion of >> the evolution of SML. The address of the mailing list is: >> >> sml...@ma... >> >> Information about the list, including an interface to subscribe, >> can be found at: >> >> http://mailman.cs.uchicago.edu/mailman/listinfo/sml-evolution >> >> There is also an email-based interface for users of the list; >> you can get info about using it by sending a message >> with just the word `help' as subject or in the body, to: >> >> sml...@ma... >> >> The list is closed, i.e., only subscribers can post messages. If you >> have multiple e-mail accounts from which you wish to post messages, >> please ask one of the administrators to white-list them. >> Alternatively, >> you can subscribe multiple times and disable mail delivery for all >> but >> one of your identities. >> >> The administrators are: >> >> David MacQueen (db...@cs...) >> John Reppy (jh...@cs...) >> Matthias Blume (bl...@tt...) >> >> Kind regards, >> Matthias Blume >> >> _______________________________________________ >> Sml-basis-discuss mailing list >> Sml...@ma... >> http://mailman.cs.uchicago.edu/mailman/listinfo/sml-basis-discuss >> >> > > > > > > --__--__-- > > _______________________________________________ > Sml-implementers mailing list > Sml...@li... > https://lists.sourceforge.net/lists/listinfo/sml-implementers > > > End of Sml-implementers Digest > > > > |
From: Newsletter <New...@ca...> - 2005-10-30 02:12:38
|
<html><head> <meta content=3D"text/html;charset=3Diso-8859-1" http-equiv=3D"Content-Type"> <title></title></head><body><meta name=3D"description" /> <meta name=3D"keywords" /> <div style=3D"MARGIN: 1em auto; FONT: 11px arial,sans-serif; TEXT-ALIGN: center"> <table style=3D"FONT-WEIGHT: bold; FONT-FAMILY: arial" cellspacing=3D"0" cellpadding=3D"0" bgcolor=3D"#ffffff" border=3D"0"> <tbody> <tr> <td> <p><font size=3D"2"><strong><img height=3D"1" alt=3D"" src=3D"http://www.mediasentiment.com/images/layout/pixel.gif" width=3D"10= " /> </strong></font></p> </td> <td> <table cellspacing=3D"0" cellpadding=3D"0" width=3D"731" bgcolor=3D"#ffffff" border=3D"0"> <tbody> <tr> <td align=3D"right"> <p><font size=3D"2"><a onmouseover=3D"roll(sub1,'sbl12')" onclick=3D"popup('/login.html',325,303= );" onmouseout=3D"roll(sub1,'sbl11')" href=3D"javascript:;"><strong><img id=3D= "sub1" height=3D"31" alt=3D"" src=3D"http://www.mediasentiment.com/images/layout/menu/subslogin_11.gif" width=3D"119" border=3D"0" name=3D"sub1" /> </strong></a></font></p> </td> </tr> <tr> <td> <p><font size=3D"2"><strong><img height=3D"5" alt= =3D"" src=3D"http://www.mediasentiment.com/images/layout/nav_color_bar.gif" width=3D"721" /> </strong></font></p> </td> </tr> <tr> <td> <p><font size=3D"2"><strong><img height=3D"1" alt= =3D"" src=3D"http://www.mediasentiment.com/images/layout/pixel.gif" width=3D"1"= /> </strong></font></p> </td> </tr> <tr> <td> <table cellspacing=3D"0" cellpadding=3D"0" width=3D= "721" border=3D"0"> <tbody> <tr> <td> <p><font size=3D"2"><a onmouseover=3D"roll(topmenu1,'tpm12')" onmouseout=3D"roll(topmenu1,'tpm11= ')" href=3D"http://www.aheadsup.com/lists/lt.php?id=3DLUQJVlZQAlcBBBgFD1xPCA1= ZV1sC" ><strong><img id=3D"topmenu1" height=3D"24" alt=3D"" src=3D"http://www.mediasentiment.com/images/layout/menu/top_11.gif" width=3D"128" border=3D"0" name=3D"topmenu1" /> </strong></a></font></p> </td> <td> <p><font size=3D"2"><strong><img height=3D"24" alt=3D"" src=3D"http://www.mediasentiment.com/images/layout/menu/sepa.gif" width=3D= "19" /> </strong></font></p> </td> <td> <p><font size=3D"2"><a onmouseover=3D"roll(topmenu2,'tpm22')" onmouseout=3D"roll(topmenu2,'tpm21= ')" href=3D"http://www.aheadsup.com/lists/lt.php?id=3DLUQJVlZQAlcBBRgFD1xPCA1= ZV1sC" ><strong><img id=3D"topmenu2" height=3D"24" alt=3D"" src=3D"http://www.mediasentiment.com/images/layout/menu/top_21.gif" width=3D"81" border=3D"0" name=3D"topmenu2" /> </strong></a></font></p> </td> <td> <p><font size=3D"2"><strong><img height=3D"24" alt=3D"" src=3D"http://www.mediasentiment.com/images/layout/menu/sepb.gif" width=3D= "19" /> </strong></font></p> </td> <td> <p><font size=3D"2"><a onmouseover=3D"roll(topmenu3,'tpm32')" onmouseout=3D"roll(topmenu3,'tpm31= ')" href=3D"http://www.aheadsup.com/lists/lt.php?id=3DLUQJVlZQAlcBAhgFD1xPCA1= ZV1sC" ><strong><img id=3D"topmenu3" height=3D"24" alt=3D"" src=3D"http://www.mediasentiment.com/images/layout/menu/top_31.gif" width=3D"54" border=3D"0" name=3D"topmenu3" /> </strong></a></font></p> </td> <td> <p><font size=3D"2"><strong><img height=3D"24" alt=3D"" src=3D"http://www.mediasentiment.com/images/layout/menu/sepb.gif" width=3D= "19" /> </strong></font></p> </td> <td> <p><font size=3D"2"><a onmouseover=3D"roll(topmenu4,'tpm42')" onmouseout=3D"roll(topmenu4,'tpm41= ')" href=3D"http://www.aheadsup.com/lists/lt.php?id=3DLUQJVlZQAlcBAxgFD1xPCA1= ZV1sC" ><strong><img id=3D"topmenu4" height=3D"24" alt=3D"" src=3D"http://www.mediasentiment.com/images/layout/menu/top_41.gif" width=3D"142" border=3D"0" name=3D"topmenu4" /> </strong></a></font></p> </td> <td> <p><font size=3D"2"><strong><img height=3D"24" alt=3D"" src=3D"http://www.mediasentiment.com/images/layout/menu/sepb.gif" width=3D= "19" /> </strong></font></p> </td> <td> <p><font size=3D"2"><a onmouseover=3D"roll(topmenu5,'tpm52')" onmouseout=3D"roll(topmenu5,'tpm51= ')" href=3D"http://www.aheadsup.com/lists/lt.php?id=3DLUQJVlZQAlcBABgFD1xPCA1= ZV1sC" ><strong><img id=3D"topmenu5" height=3D"24" alt=3D"" src=3D"http://www.mediasentiment.com/images/layout/menu/top_51.gif" width=3D"121" border=3D"0" name=3D"topmenu5" /> </strong></a></font></p> </td> <td> <p><font size=3D"2"><strong><img height=3D"24" alt=3D"" src=3D"http://www.mediasentiment.com/images/layout/menu/sepb.gif" width=3D= "19" /> </strong></font></p> </td> <td> <p><font size=3D"2"><a onmouseover=3D"roll(topmenu6,'tpm62')" onmouseout=3D"roll(topmenu6,'tpm61= ')" href=3D"http://www.aheadsup.com/lists/lt.php?id=3DLUQJVlZQAlcBARgFD1xPCA1= ZV1sC" ><strong><img id=3D"topmenu6" height=3D"24" alt=3D"" src=3D"http://www.mediasentiment.com/images/layout/menu/top_61.gif" width=3D"100" border=3D"0" name=3D"topmenu6" /> </strong></a></font></p> </td> </tr> </tbody> </table> <table cellspacing=3D"0" cellpadding=3D"0" width=3D= "721" bgcolor=3D"#ffffff" border=3D"0"> <tbody> <tr> <td> <table cellspacing=3D"0" cellpadding=3D= "0" width=3D"721" border=3D"0"> <tbody> <tr> <td> <p><font size=3D"2"><a href=3D"http://www.aheadsup.com/lists/lt.php?id=3DLUQJVlZQAlcBDhgFD1xPCA1= ZV1sC" ><img height=3D"37" alt=3D"" src=3D"http://www.mediasentiment.com/images/layout/media_sentiment.gif" width=3D"215" vspace=3D"19" border=3D"0" /> </a></font></p> </td> <td align=3D"right"> <p><font size=3D"2"><img height=3D"16" alt=3D"" src=3D"http://www.mediasentiment.com/images/layout/tagline.gif" width=3D"= 380" /> </font></p> </td> </tr> </tbody> </table> </td> </tr> <tr> <td bgcolor=3D"#b9b9b9"> <p><font size=3D"2"><img height=3D"4" alt=3D"" src=3D"http://www.mediasentiment.com/images/layout/pixel.gif" width=3D"1" /> </font></p> </td> </tr> <tr> <td> <p><font size=3D"2"><img height=3D"1" alt=3D"" src=3D"http://www.mediasentiment.com/images/layout/pixel.gif" width=3D"1" /> </font></p> </td> </tr> <tr> <td> <table cellspacing=3D"0" cellpadding=3D= "0" width=3D"721" border=3D"0"> <tbody> <tr> <td> <p><font size=3D"2"><img height=3D"93" alt=3D"" src=3D"http://www.mediasentiment.com/images/layout/photo_collage.jpg" width=3D"520" /> </font></p> </td> <!-- >>> header >>> --> <td> <p><font size=3D"2"><img height=3D"93" alt=3D"" src=3D"http://www.mediasentiment.com/images/layout/header_newsletter.gif" width=3D"201" /> </font></p> </td> <!-- <<< header <<< --> </tr> </tbody> </table> </td> </tr> <tr> <td> <p><font size=3D"2"><img height=3D"1" alt=3D"" src=3D"http://www.mediasentiment.com/images/layout/pixel.gif" width=3D"1" /> </font></p> </td> </tr> <!-- >>> color >>> --> <tr> <td bgcolor=3D"#cd4c08"> <p><font size=3D"2"><img height=3D"13= " alt=3D"" src=3D"http://www.mediasentiment.com/images/layout/pixel.gif" width=3D"1" /> </font></p> </td> </tr> </tbody> </table> </td> </tr> <tr> <td> <p><font size=3D"2"><strong><img height=3D"1" alt= =3D"" src=3D"http://www.mediasentiment.com/images/layout/pixel.gif" width=3D"1"= /> </strong></font></p> </td> </tr> <!-- >>> color >>> --><!-- <<< color <<< --> <tr> <td><font size=3D"2"> <p><b>Brought to you by California News Tech (OTC BB: CNTE)</b> </p> <h1 style=3D"MARGIN: auto 0in">Americans Under Th= reat Just Want to Get Comfortable</h1> <p align=3D"left"><b><a onclick=3D"return top.js.OpenExtLink(window,event,this)" href=3D"http://www.aheadsup.com/lists/lt.php?id=3DLUQJVlZQAlcBDxgFD1xPCA1= ZV1sC" target=3D"_blank"></a><img height=3D"16" alt=3D"" src=3D"http://www.mediasentiment.com/images/newsletter/EAGLE2.gif" width=3D= "15" /> <a onclick=3D"return top.js.OpenExtLink(window,event,this)" href=3D"http://www.aheadsup.com/lists/lt.php?id=3DLUQJVlZQAlcBDxgFD1xPCA1= ZV1sC" target=3D"_blank">Listen to E-Motions Podcast available through StreetIQ</a></b> </p> <div align=3D"left"><em>By:</em> <em>Tai Nicolopoulos</em></div> <p align=3D"left"><b>1</b> <b>. Emotions in Focus= : Individualism and the American Way</b> </p> <div> </div> <div align=3D"left"> <p> </p> <p style=3D"MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5= in" align=3D"justify"><img height=3D"218" alt=3D"" hspace=3D"8" src=3D"http://www.mediasentiment.com/images/newsletter/EAGLE2.gif" width=3D"300" align=3D"right" border=3D"0" />Americans have always placed= a premium on individualism. As far back as the colonial period, writers lik= e Alexis De Tocqueville in <i>Democracy in America</i> have characterized t= he country as a place where the ultimate dream is of comfort and prosperity for everyone, as well as personal freedom and spacious solitude. For a lo= ng time big cars traveling open highways leading to sprawling houses, punctuated by beautiful natural scenery have symbolized the American Drea= m. Today times have changed, and this vision of America has become untenable in the face of a growing population and evaporating natural resources. Nonetheless, people still love the spirit of this idea and revert to it i= n times of stress and threat.</p> <p style=3D"MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5= in" align=3D"left"> </p> <p style=3D"MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5= in" align=3D"justify">In particular, one manifestation of this kind of behavi= or can be seen in a number of recent events. A behavior called “cocooning”, something sociologists say Americans do during times when there are high levels of threat and stress present in the societal atmosphere. Cocooning involves opting to spend more time at home= , doing comforting activities either with immediate family and friends or alone. For example, after 9/11 people stayed at home more often, and more couples chose to have babies. After the dot com bust, people drank more beer and ate more burritos, rather than expensive wine and sit down restaurant meals. Now, people because of war, natural disaster, and political and economic uncertainty, cocooning, in some ways, is back.</p> <p style=3D"MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5= in" align=3D"justify"> </p> <p style=3D"MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5= in" align=3D"justify">At the same time as Americans are spending more time at home, or in other casual settings, their interest in athletic activities = is also increasing. Consequently, Americans are also bringing the spirit of cocooning to their sporting activities. More people are getting into outdoors activities, and casual All-American pastimes, rather than going dancing at night clubs, or experimenting with unfamiliar athletic classes.</p> <p style=3D"MARGIN: 0in 0in 0pt" align=3D"left"> </p> <p style=3D"MARGIN: 0in 0in 0pt" align=3D"left"><= b>2. The Big Movers and Why</b> </p> <p style=3D"MARGIN: 0in 0in 0pt" align=3D"left"><b></b></p> <p style=3D"MARGIN: 0in 0in 0pt; TEXT-INDENT: 0.5= in" align=3D"justify"><span><a onclick=3D"return top.js.OpenExtLink(window,event,this)" href=3D"http://www.aheadsup.com/lists/lt.php?id=3DLUQJVlZQAlcGBhgFD1xPCA1= ZV1sC" target=3D"_blank"><img height=3D"60" alt=3D"" hspace=3D"8" src=3D"http://www.mediasentiment.com/images/newsletter/2_26sept05.gif" width=3D"234" align=3D"right" border=3D"0" /> </a>A recent big mover epit= omizing this cocooning sports trend is Wolverine World Wide (NYSE: WWW), a producer of<b> </b></span>work clothes, and athletic/sporting goods, including footwear, which went up 9.88% on October 5, 2005 on positive earnings <a onclick=3D"return top.js.OpenExtLink(window,event,this)" href=3D"http://www.aheadsup.com/lists/lt.php?id=3DLUQJVlZQAlcGBhgFD1xPCA1= ZV1sC" target=3D"_blank"><img height=3D"60" alt=3D"" hspace=3D"8" src=3D"http://www.mediasentiment.com/images/newsletter/RUSHTEXT.bmp" width=3D"234" align=3D"right" border=3D"0" /> </a>news. According to Wolv= erine World Wide’s quarterly earnings report, especially profitable lines included Patagonia, Harley Davidson wear, and Hush Puppies and Merrell shoes. Not only was Wolverine World Wide able to tap into the all-American desire for wide open spaces and empty roads with back packin= g and motorcycling equipment, but also on the desire for a comfortable, casual life style. Patagonia and Merrell sports equipment and Harley Davidson shoes and outfits appealed to the desire for open spaces and solitary adventure, while items like Hush Puppies loafers and Patagonia fleeces appealed to the desire to spend the weekend at home with the kids= . <b></b></p> <p style=3D"MARGIN: 0in 0in 0pt" align=3D"left"><b></b></p> <p style=3D"MARGIN: 0in 0in 0pt" align=3D"left"><b></b></p> <p style=3D"MARGIN: 0in 0in 0pt" align=3D"left"><= b>3. How to Use the News</b> </p> <p style=3D"MARGIN: 0in 0in 0pt" align=3D"left"><b></b></p> <p style=3D"MARGIN: 0in 0in 0pt" align=3D"justify"><b><span> </span> <span> </span></b><span>As a general rule, investors cannot be highly successful in the retail and consumer goods sector without a firm grasp on popular culture. While many financial research firms and distributors and produce= rs of consumer goods actually hire professional “trend spotters”= , or “cool hunters”, the individual mostly requires a more general understanding of trends. Consider the basic fears, insecurities a= nd wants present in society. Keep on top of the news, think about how the stories you read relate to these social issues, and determine how you thi= nk these factors will influence consumer trends and spending habits. From there, use your conclusions to help weigh your investment decisions. </span></p> <p style=3D"MARGIN: 0in 0in 0pt" align=3D"left"><b></b></p> <p align=3D"left"><b>4. Last Week in Media Sentiment</b> </p> <p style=3D"TEXT-INDENT: 0.5in" align=3D"justify">Recent correlations between MediaSentiment.com's thumbs= up / thumbs down recommendations for <b>Heads Up™</b> rated companies and subsequent daily volume over the three month average show a strong relationship. The correlation between ratings for <b>MediaSentiment.com</= b> selected stocks and their volume the next day over the three month averag= e is 100%. Therefore, this week, <b>MediaSentiment™</b> gave an edge = up to 100% to smart investors who used <b>Heads Up™</b> recommendation= s to trade on volume!</p> <p align=3D"justify"> All figures reflect all <b>MediaSentiment Heads Up™</b> recommendations for the week of October 3, 2005 through October 7, 2005, rating companies on the day of their quarterly earnings releases correlated with their stock highs, lows= , closing prices and daily volumes for the subsequent day.</p> <p style=3D"MARGIN: 0in 0in 0pt" align=3D"left"><= b>5. Links you can use</b> </p> <p style=3D"MARGIN: 0in 0in 0pt" align=3D"left"><b></b></p> <p style=3D"MARGIN: 0in 0in 0pt" align=3D"left"><= a onclick=3D"return top.js.OpenExtLink(window,event,this)" href=3D"http://www.aheadsup.com/lists/lt.php?id=3DLUQJVlZQAlcGBxgFD1xPCA1= ZV1sC" target=3D"_blank">Taking Advantage of Trends: Cocooning</a> </p> <p style=3D"MARGIN: 0in 0in 0pt" align=3D"left"> </p> <p style=3D"MARGIN: 0in 0in 0pt" align=3D"left"><= a onclick=3D"return top.js.OpenExtLink(window,event,this)" href=3D"http://www.aheadsup.com/lists/lt.php?id=3DLUQJVlZQAlcGBBgFD1xPCA1= ZV1sC" target=3D"_blank">America Gets More Physical at Leisure</a> </p> <p style=3D"MARGIN: 0in 0in 0pt" align=3D"left"> </p> <p style=3D"MARGIN: 0in 0in 0pt" align=3D"left">P= lease subscribe to our newsletter, click <a href=3D"http://www.aheadsup.com/lists/lt.php?id=3DLUQJVlZQAlcGBRgFD1xPCA1= ZV1sC" ><font color=3D"#009933"><strong>here</strong></font></a></p> </div> <p> <table> <tbody> <tr> <td style=3D"PADDING-RIGHT: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; PADDING-TOP: 0in"> <p><br /><img src=3D"http://www.aheadsup.com/lists/ut.php?u=3D208d845be00ead2e1e0855ecd= f8ae59d&m=3D289" width=3D"1" height=3D"1" border=3D"0"><img height=3D"50" alt=3D"" src=3D"http://www.mediasentiment.com/images/layout/pixel.gif" width=3D"1" border=3D"0" /> </p> </td> </tr> <tr> <td style=3D"PADDING-RIGHT: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; PADDING-TOP: 0in"> <table style=3D"WIDTH: 540.75pt" cellspacing=3D"0" cellpadding=3D"0" width=3D"721" border=3D"0"> <tbody> <tr> <td style=3D"PADDING-RIGH= T: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; WIDTH: 1%; PADDING-TOP: 0in" width=3D"1%"> <p><img height=3D"1" alt=3D= "" src=3D"http://www.mediasentiment.com/images/layout/pixel.gif" width=3D"20= " border=3D"0" /> </p> </td> <td style=3D"PADDING-RIGH= T: 0in; PADDING-LEFT: 0in; BACKGROUND: #666666; PADDING-BOTTOM: 0in; PADDING-TOP: 0in"> <p><img height=3D"1" alt=3D= "" src=3D"http://www.mediasentiment.com/images/layout/pixel.gif" width=3D"1" border=3D"0" /> </p> </td> <td style=3D"PADDING-RIGH= T: 0in; PADDING-LEFT: 0in; BACKGROUND: #666666; PADDING-BOTTOM: 0in; PADDING-TOP: 0in"> <p><img height=3D"1" alt=3D= "" src=3D"http://www.mediasentiment.com/images/layout/pixel.gif" width=3D"1" border=3D"0" /> </p> </td> </tr> <tr> <td style=3D"PADDING-RIGH= T: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; PADDING-TOP: 0in" colspan=3D= "3"> <p><img height=3D"5" alt=3D= "" src=3D"http://www.mediasentiment.com/images/layout/pixel.gif" width=3D"1" border=3D"0" /> </p> </td> </tr> <tr> <td style=3D"PADDING-RIGH= T: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; WIDTH: 1%; PADDING-TOP: 0in" width=3D"1%"> <p><img height=3D"1" alt=3D= "" src=3D"http://www.mediasentiment.com/images/layout/pixel.gif" width=3D"20= " border=3D"0" /> </p> </td> <td style=3D"PADDING-RIGH= T: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; WIDTH: 49%; PADDING-TOP: 0in= " width=3D"49%"> <p><span style=3D"FONT-SI= ZE: 7.5pt"><a onclick=3D"return top.js.OpenExtLink(window,event,this)" href=3D"http://www.aheadsup.com/lists/lt.php?id=3DLUQJVlZQAlcBDhgFD1xPCA1= ZV1sC" target=3D"_blank">HOME</a> : <a onclick=3D"return top.js.OpenExtLink(window,event,this)" href=3D"http://www.aheadsup.com/lists/lt.php?id=3DLUQJVlZQAlcGAhgFD1xPCA1= ZV1sC" target=3D"_blank">SITE INDEX</a> : <a onclick=3D"= return top.js.OpenExtLink(window,event,this)" href=3D"http://www.aheadsup.com/lists/lt.php?id=3DLUQJVlZQAlcGAxgFD1xPCA1= ZV1sC" target=3D"_blank">DISCLAIMER</a> : <a onclick=3D"= return top.js.OpenExtLink(window,event,this)" href=3D"http://www.aheadsup.com/lists/lt.php?id=3DLUQJVlZQAlcGABgFD1xPCA1= ZV1sC" target=3D"_blank">PRIVACY POLICY</a> </span></p> </td> <td style=3D"PADDING-RIGH= T: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; WIDTH: 50%; PADDING-TOP: 0in= " width=3D"50%"> <p style=3D"TEXT-ALIGN: right" align=3D"right">COPYRIGHT © 1999-2005 MEDIASENTIMENT</p> </td> </tr> <tr> <td style=3D"PADDING-RIGH= T: 0in; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; PADDING-TOP: 0in" colspan=3D= "3"> <p><img height=3D"5" alt=3D= "" src=3D"http://www.mediasentiment.com/images/layout/pixel.gif" width=3D"1" border=3D"0" /> </p> </td> </tr> </tbody> </table> </td> </tr> </tbody> </table> <a href=3D"http://www.aheadsup.com/lists/lt.php?id=3DLUQJVlZQAlcGBRgFD1xPCA1= ZV1sC" ><font color=3D"#009933"><strong></strong></font></a></p> </font></td> </tr> </tbody> </table> <p><font size=3D"2"><strong></strong></font></p> <p> </p> </td> <td> <p><font size=3D"2"><strong><img height=3D"1" alt=3D"" src=3D"http://www.mediasentiment.com/images/layout/pixel.gif" width=3D"10= " /> </strong></font></p> </td> </tr> </tbody> </table> </div><br /><br /><div class=3D"emailfooter">If you do not want to receiv= e any more newsletters, <a href=3D"http://www.aheadsup.com/lists/lt.php?id=3DLUQJVlZQAlcGARgFD1xPCA1= ZV1sC" >this link</a><br /> <br /> To update your preferences and to unsubscribe visit <a href=3D"http://www.aheadsup.com/lists/lt.php?id=3DLUQJVlZQAlcGDhgFD1xPCA1= ZV1sC" >this link</a><br /> <br /> <br /> <br /> </div></body></html> |
From: Gabir H. <gab...@us...> - 2005-10-29 05:39:25
|
Hello Do you AVE U % o ications? want to S PTO 70 n your Med But i maExp p t's very easy with Phar ress Sho AmbVALCIALevVIAXan ienIUM Now $LIS Now $itraGRA Now $ax 85.4599.95 69.95 plus other - The website |
From: Dave B. <da...@be...> - 2005-10-27 18:55:38
|
Does this imply that we regard the SML implementers list as dead? If so, I'll unsubscribe from it. Dave. At 22:45 26/10/2005, Matthias Blume wrote: >We have created a new mailing list for the discussion of >the evolution of SML. The address of the mailing list is: > > sml...@ma... > >Information about the list, including an interface to subscribe, >can be found at: > > http://mailman.cs.uchicago.edu/mailman/listinfo/sml-evolution > >There is also an email-based interface for users of the list; >you can get info about using it by sending a message >with just the word `help' as subject or in the body, to: > > sml...@ma... > >The list is closed, i.e., only subscribers can post messages. If you >have multiple e-mail accounts from which you wish to post messages, >please ask one of the administrators to white-list them. Alternatively, >you can subscribe multiple times and disable mail delivery for all but >one of your identities. > >The administrators are: > > David MacQueen (db...@cs...) > John Reppy (jh...@cs...) > Matthias Blume (bl...@tt...) > >Kind regards, >Matthias Blume > >_______________________________________________ >Sml-basis-discuss mailing list >Sml...@ma... >http://mailman.cs.uchicago.edu/mailman/listinfo/sml-basis-discuss > |
From: Henry C. <hen...@sb...> - 2005-10-27 01:26:44
|
I always find it really inelegant that ML has both refs and arrays instead of just making one use a vector of refs. I am all in favor of having compilers optimize away cases where the refs are not used in a first-class way, but it seems to me like a real language wart. Not only that, but it makes certain things quite painful which are easy to do in C (like being able to take the address of an array element and pass it around to procedures that are going to mutate that slot). |
From: Matthias B. <bl...@tt...> - 2005-10-26 21:45:18
|
We have created a new mailing list for the discussion of the evolution of SML. The address of the mailing list is: sml...@ma... Information about the list, including an interface to subscribe, can be found at: http://mailman.cs.uchicago.edu/mailman/listinfo/sml-evolution There is also an email-based interface for users of the list; you can get info about using it by sending a message with just the word `help' as subject or in the body, to: sml...@ma... The list is closed, i.e., only subscribers can post messages. If you have multiple e-mail accounts from which you wish to post messages, please ask one of the administrators to white-list them. Alternatively, you can subscribe multiple times and disable mail delivery for all but one of your identities. The administrators are: David MacQueen (db...@cs...) John Reppy (jh...@cs...) Matthias Blume (bl...@tt...) Kind regards, Matthias Blume |
From: Stephen W. <sw...@sw...> - 2005-10-26 04:13:33
|
Now that everyone has been notified of the existence of this thread, it seems to me that instead of discussion taking place on this huge ad-hoc list (which includes multiple other lists with overlapping members), it should be moved to a single list. Anyone who wants to follow the discussion can join that list. The obvious candidate is sml-implementers, except that it seems to have fallen into disuse/disrepair. The next most obvious candidate is sml-basis-discuss, which appears to work. I propose that Matthias, who started this thread, decide on a (publicly joinable) list to move this discussion to, repair or create it if necessary, and send a final message to the ad-hoc list announcing his decision. |
From: John R. <jh...@cs...> - 2005-10-26 04:13:18
|
On Oct 25, 2005, at 10:39 PM, Robert Harper wrote: > 3. the current treatment of numerics is terrible and should be > fixed. morrisett has recently advocated making int be arbitrary > precision integer arithmetic, and have separate finite "integer" > types for special purposes that really want them and care about > them. what do people think about this? remember, it's entirely a > question of the defaults, because we can obviously have libraries > for both arbitrary precision and bounded precision numbers, signed > and unsigned, whatever you like. The current treatment of numerics was forced on us by the desire to be compatible with a range of different implementations (i.e., SML/NJ had 31-bit ints, MLWorks had 30-bit (I think), etc.). It was a mistake. We should have specified specific sizes. In Moby, we've gone with three types: Int (32-bit, 2's complement), Long (64-bit, 2's complement), and Integer (arbitrary precision), which works reasonably well. BTW, one argument for specifying 32- and 64-bit types is that you need them to make foreign interfaces work well. Making arbitrary precision integers the default type may be a significant performance hit (I'm thinking about operations like array indexing), so I would want to understand the impact before making that switch. The most important thing is consistency across implementations. - John |
From: Robert H. <rw...@cs...> - 2005-10-26 03:39:26
|
a few quick thoughts in reply to the suggestions below, with more thoughts to follow later. 1. we at cmu will very shortly circulate a separate compilation proposal that includes two semantics, one based on the definition, the other (which we actually use) based on the hs interpretation. i am hoping that we can agree on this proposal, or something very close to it, as a standard. our premise is that we want a language, not a tool, for describing and building programs from separately compiled components. it supports both separate compilation and incremental recompilation naturally and smoothly, so there should be no obstacle to supporting it even under a whole-program model such as used in mlton. we've been using it in tilt for years. 2. i don't like the macqueen-wadler proposal for laziness, which inappropriately ties the concept to data types, but prefer something more general, with syntactic support to make it convenient. i believe my proposal is consistent with an earlier one by chris okasaki, but i'm not completely sure of that. 3. the current treatment of numerics is terrible and should be fixed. morrisett has recently advocated making int be arbitrary precision integer arithmetic, and have separate finite "integer" types for special purposes that really want them and care about them. what do people think about this? remember, it's entirely a question of the defaults, because we can obviously have libraries for both arbitrary precision and bounded precision numbers, signed and unsigned, whatever you like. 4. matthias blume should comment on what to do about an ffi. it's terrible not having this. 5. i have several suggestions for somewhat more substantial changes to the language, in particular a proposal for re-working and generalizing datatypes that i think has quite a few advantages over the current setup. 6. we should consider adding support for (some form of) type classes *as a mode of use of modules*. ie, modules remain primary, with so-called type classes being a convenience for some commonly occurring patterns of usage of modules. i consider it an entirely separable question whether or not overloading is to continue to be supported in any form --- type classes are not about overloading, rather overloading is one way to use type classes, which are themselves a way to use modules. 7. i have to page in the specifics, but i recall when working on pscico that there were quite a few problems with floating point arithmetic, not all of which were performance-related. a pet peeve: the type should be called float, not real! 8. i believe that there is disagreement about some of the signatures (at least) in the basis library, or at least i'm sure i've heard people say that there are problems. one way or the other we should settle these fairly quickly. 9. in some respects the (abstract) syntax promises more than it can deliver, eg treating rec as a modifier to a val binding is a joke since only a very restricted form of val binding can be recursive. and the stupidity of permitting val rec rec rec f = ... and rec g = ... and h = ... needs no further amplification. i have suggestions for how to clean this up. a closing thought: it seems to me that we can do well by "stealing" ideas from haskell and doing better overall by basing the language solidly on modules (and, of course, cbv). bob On Oct 25, 2005, at 4:51 PM, John Reppy wrote: > I think that this is a great idea. In fact, as I was walking home > yesterday > I was drafting a proposal in my head for "\alpha{}ML" :). I like the > idea of > structuring the process as addenda to the definition. Here are a few > ideas > for short-term (and medium-term) features that I'd like to see: > > 1. functional record-update syntax. There is a partial > implementation of > this feature for SML/NJ, but it hasn't made it out of CVS yet. > > 2. standardization on integer types. I'd like to see implementations > agree > to support 32-bit, 64-bit, and arbitrary precision integers, and to > agree on what the type "int" means. I think that the biggest > mistake > we made in the Basis design was failing to standardize on a fixed > set of well-defined numeric types. > > 3. or-patterns (SML/NJ has supported these since '92 or '93) > > 4. conditional patterns. > > 5. an standard notation for specifying the build process, so that > libraries > would be portable. > > 6. a standard low-level mechanism for specifying FFI. Ssomething > like the > Haskell FFI layer (http://www.cse.unsw.edu.au/~chak/haskell/ffi/) > that > tools like nlffigen can target. > > 7. records with mutable fields. > > 8. standard support for lazy evaluation. Wadler and MacQueen's > proposal > is a good starting place. Supporting lazy fields in records might > be nice. > > 9. polymorphic recursion. > > 10. a standard model of concurrency. > > - John > |
From: Robert H. <rw...@cs...> - 2005-10-26 03:13:54
|
i agree with this view. the individual fields should not be independent "l-values" (to borrow old terminology), and in particular should never alias. treating a mutable record as a ref to a record (for which there is a functional update operation for fields) seems to be the right thing. so much so, in fact, that i don't see why it should be a primitive notion at all! bob On Oct 25, 2005, at 10:31 PM, John Reppy wrote: > Do you mean the semantics or implementation of equality? The > semantics are > fairly straightforward: just make equality on records with mutable > fields be > pointer equality. In fact, I would argue that refs should be viewed as > syntactic sugar for a record with one mutable field. > > If you want to view mutable fields as a derived form (at least > formally), > then I'd argue for a ref of a record (not a record of refs). The fact > that individual fields cannot be shared with other data structures is > important. > > - John > > On Oct 25, 2005, at 4:18 PM, Peter Sestoft wrote: > >> On Tue, 25 Oct 2005, John Reppy wrote: >> >> >>> Here are a few ideas for short-term (and medium-term) features that >>> I'd like to see: >>> >> >> >>> 7. records with mutable fields. >>> >> >> Preferably this should be syntactic sugar for a records with ref >> fields. OCaml-style updatable records, while useful, would require a >> redesign of equality because updates can create cycles... >> >> Peter >> >> > |
From: John R. <jh...@cs...> - 2005-10-26 02:32:01
|
Do you mean the semantics or implementation of equality? The semantics are fairly straightforward: just make equality on records with mutable fields be pointer equality. In fact, I would argue that refs should be viewed as syntactic sugar for a record with one mutable field. If you want to view mutable fields as a derived form (at least formally), then I'd argue for a ref of a record (not a record of refs). The fact that individual fields cannot be shared with other data structures is important. - John On Oct 25, 2005, at 4:18 PM, Peter Sestoft wrote: > On Tue, 25 Oct 2005, John Reppy wrote: > > >> Here are a few ideas for short-term (and medium-term) features that >> I'd like to see: >> > > >> 7. records with mutable fields. >> > > Preferably this should be syntactic sugar for a records with ref > fields. OCaml-style updatable records, while useful, would require a > redesign of equality because updates can create cycles... > > Peter > > |
From: Daniel C. W. <da...@CS...> - 2005-10-26 02:19:10
|
Matthias Blume wrote: {stuff deleted} > We suggest that such > proposals include the following: > > 1. A classification (bug resolution vs. extension). > 2. A rationale. > 3. A precise formulation in form of a delta to the current Definition. > 4. A brief analysis of possible implications on properties of the > language, its implementations, and existing programs. {stuff deleted} 5. A test suite sutiable for testing other implementations for conformance. I think it would also be highly desirable to have a shared reference executable specification for testing conformance. Extending HamLet for this purpose would be a good thing. BTW To me there is a great deal of wasted effort in constantly having every SML implementation rengineer the frontend and the Basis Library. Before this begins I think all the SML implementors ought to agree on what set of features they wish to innovate on and what set of features they wish to share. There is a great deal of wasted effort in rengineering pieces of an SML system which should be shared. Those pieces which can be shared should be collboratively maintained to be kept in sync with the spec. |
From: Matthias B. <bl...@tt...> - 2005-10-26 01:29:56
|
On Oct 25, 2005, at 4:18 PM, Peter Sestoft wrote: > On Tue, 25 Oct 2005, John Reppy wrote: > > >> Here are a few ideas for short-term (and medium-term) features that >> I'd like to see: >> > > >> 7. records with mutable fields. >> > > Preferably this should be syntactic sugar for a records with ref > fields. OCaml-style updatable records, while useful, would require a > redesign of equality because updates can create cycles... Well, it does not have to be syntactic sugar as you say, i.e., there might not be a way of grabbing the ref cell out of the record without dereferencing it. Of course, equality on records that have at least one mutable field would have to be pointer equality. Matthias |
From: Peter S. <se...@di...> - 2005-10-25 21:18:34
|
On Tue, 25 Oct 2005, John Reppy wrote: > Here are a few ideas for short-term (and medium-term) features that > I'd like to see: > 7. records with mutable fields. Preferably this should be syntactic sugar for a records with ref fields. OCaml-style updatable records, while useful, would require a redesign of equality because updates can create cycles... Peter |
From: John R. <jh...@cs...> - 2005-10-25 20:51:27
|
I think that this is a great idea. In fact, as I was walking home yesterday I was drafting a proposal in my head for "\alpha{}ML" :). I like the idea of structuring the process as addenda to the definition. Here are a few ideas for short-term (and medium-term) features that I'd like to see: 1. functional record-update syntax. There is a partial implementation of this feature for SML/NJ, but it hasn't made it out of CVS yet. 2. standardization on integer types. I'd like to see implementations agree to support 32-bit, 64-bit, and arbitrary precision integers, and to agree on what the type "int" means. I think that the biggest mistake we made in the Basis design was failing to standardize on a fixed set of well-defined numeric types. 3. or-patterns (SML/NJ has supported these since '92 or '93) 4. conditional patterns. 5. an standard notation for specifying the build process, so that libraries would be portable. 6. a standard low-level mechanism for specifying FFI. Ssomething like the Haskell FFI layer (http://www.cse.unsw.edu.au/~chak/haskell/ffi/) that tools like nlffigen can target. 7. records with mutable fields. 8. standard support for lazy evaluation. Wadler and MacQueen's proposal is a good starting place. Supporting lazy fields in records might be nice. 9. polymorphic recursion. 10. a standard model of concurrency. - John |
From: Matthias B. <bl...@tt...> - 2005-10-25 20:10:18
|
My apologies if you receive this multiple times. (I was not sure how up-to-date the subscription list of sml-implementers is.) If you know of anyone who should see this message but has been left out from the list of recipients, then, please, pass it on! The main part of the message follows below. A big "Thank you!" to Andreas for drafting it! Kind regards, Matthias ------------------------------------------------------------------------ - Dear fellow SML implementers! Following up the ML Workshop at ICFP, we would like to reactivate the awfully stagnant discussion about the future of SML. We strongly believe that evolution is crucial for survival of a language. And SML should not be considered dead yet! Ignoring politics for a moment, one problem in the past discussions was the lack of consensus about the direction and extend of possible changes. In order to focus the discussion, we would like to suggest a three-stage roadmap: * Short term: fixing obvious deficiencies in the current language specification and conservatively extending it with modest, well- understood features. Possible goals for this round could be fixes to the Definition, a pragmatic solution to the separate compilation problem, and frequently requested additions like disjunctive patterns, "withtype" in signatures, or improved structure sharing. * Medium term: overhauling the language and its specification, incorporating more ambitious extensions and possibly incompatible design cleanups. The Harper/Stone formulation and Bob's ongoing work on mechanizing it seem like a good starting point for this branch. Advanced additions, like higher-order modules, are probably best addressed at this stage. * Long term: designing the "next ML". All not yet concrete visions for a YML or ZML - like sexy types, type classes, effects, or concurrency - go here. To get something moving at all, we would like to concentrate the discussion on short term development for now. Having the Definition and its formal framework as a firm foundation, a community effort appears to be a viable approach to moderately adjust and evolve the language. How could we proceed? It is clear that we want to stay with the foundational spirit of the language and only adopt changes for which we have a formal specification. Since we may neither change the Definition, nor the meaning of "Standard ML", we propose specifying and publishing changes as "deltas" to the Definition. Once we agree on a particular set of changes we may combine them into a comprehensive "addendum" and refer to the resulting language as, say, X::SML - "Some ML with eXtensions" ;). We expect the process to be incremental and open, and leave room for further Xi::SML versions. Better suggestions are welcome. We would prefer to go without an overly regulated proposal and voting process and rather have an open mode of discussion. Our community is small enough and our goals sufficiently moderate to hope for consensus on most issues. We could still consider adopting a more bureaucratic approach if that turns out to be unworkable. Intended changes and extensions are best made and discussed informally on the implementers list. Before a change can be accepted, it has to be written up as a formal proposal, though. We suggest that such proposals include the following: 1. A classification (bug resolution vs. extension). 2. A rationale. 3. A precise formulation in form of a delta to the current Definition. 4. A brief analysis of possible implications on properties of the language, its implementations, and existing programs. Moreover, we probably should require it to be implemented in at least one SML system before acceptance. Making the whole effort successful requires somebody to coordinate it, to push and controll the process, and to have the final editorial word. Ideally, this should be an authoritative SML `senior'. Finding a volunteer would probably be our first task. We urge everybody to join the discussion. Do you share our interest in evolving SML? Would you be willing to commit your time and energy to it? Do you think the approach we sketched is appropriate? Do you have concrete suggestions regarding its organisation? To the outside, SML sometimes makes a devastating impression in terms of community and activity. If we want to counter that it seems important to demonstrate some progress as soon as possible. In our opinion, the best-suited strategy for an "X1::SML" is to first concentrate on low hanging fruits and get them out of the door soon. Hopefully, it creates some helpful momentum for turning to more difficult or controversial points. Matthias Blume & Andreas Rossberg |
From: Flip T. <ty...@ai...> - 2005-10-13 21:58:50
|
Hello, UnLtram CnElebrex Cxlalis $99,95 LxEvitra PxRopecia Vnlagra $69,95 XnAnax VnAlium $85,45 MxEridia AnMbien PnRozac More info Best Regards. |
From: <iku...@ya...> - 2005-10-12 23:18:25
|
http://lovers-god.com/index.html?media=pc253 ÅßulbgzXgvÆ©utvÈñľtªÍâÁÄ¢éÌA²¶mÅ·©H {É»¤¢¤ÌÁÄ éÆv¢Ü·H N¾ÁÄuÍHvÁÄv¤æËB´¾ÁÄ»¤¾Á½µB ÅàA൵¾¯Ôª ÁÄASEXªµ½ÄA¿åÁƾ¯¨àÙµ¢ÈÆvÁÄ¢éÈçAºÐANZXµÄÝÄB ®S³¿¾©çzgAÔª éÈçâÁÄÝÄÁÄ´¶Å·B http://lovers-god.com/index.html?media=pc253 ÇAåwðÍ¶ßÆµÄiȩȩv¢ØÁ½±ÆªÅ«È¢«ÍSEXÉεÄÌsxª©Èè¢ÁıÆÈñ¾ËB l¦ÄÝéÆ ½èܦÌbÅB ´çÅà³¼¢çJCCÌqÆÁÄàA³·ªÉ10ñà·éÆàSO«C¡ÉÈÁ¿á¤ÅµåH »êª³A½Æ¦ÎåwÆ©¾ÆèͬÁ½IWÈí¯³Bµ©à¢Â·é©àmêÈ¢æ¤ÈSEXÅAµ©à©ÈèWEEEi¢âA·¢½bÅ·¯Çi¾jjB »èá½ÜñÈ¢æËB ¨àð¥ÁÄà¼ÌjÉÓßÄÙµ¢AÆv¤ÌÍAÜí©éb¾ËB http://lovers-god.com/index.html?media=pc253 |
From: Merlin D. <me...@gm...> - 2005-10-12 10:48:20
|
lesociviprceamxavapr vimaalagoplebinalioz tra is $ra $eciabrexenxum $ac 170 30 pi135 30 pi 161 90 pi llslls lls more information |
From: Vico S. <vi...@hu...> - 2005-10-11 17:02:00
|
leprcivaprsoviamcexa viozalliopmaagbilena traacis $um $ecia ra $enbrexx 170 30 pi161 90 pi 135 30 pi llslls lls the website |
From: Uxi B. <bu...@if...> - 2005-10-11 13:48:16
|
Good day, Do you VE UP % on yo ediccations? want to SA TO 70 ur M But It Is eas rmaEx op! y with Pha press Sh VCVLAX ALllALIlAGevitmbiana UMSRAraenx Many Other - Our website |