Re: Pragmatic Requirements Summary : update

> 	That is roughly a restatement of our mission statement... The only 
> real sticking place is where the HW forced paradigm stops and the SW one 
> starts... If we stay on track we should defently have strawman 2 out by this 
> weekend if not sooner... We have 3 relativally competing goals and only 1 of 
> them has a clear solution so far they are (note I am purposally saying which 
> one is the sticking point because I want to see what people have to say about 
> each one with no bias): 
>  
> 	1) How to seperate code from data in a clean generic paradigm neutral 
manner 
 
 We are still arguing about this one. I put forth that code is just another form of 
data and should be treated as such, Aryeh has yet to concede to my inevitable 
victory ;) 
 
> 	2) How to handle situations where the syntax/semantics of one paradigm 
clashs with 
> 	   that of an other 
 
 This is currently a huge open area we need to address. Hopefully once the site is 
up we can start recruiting volunteers to look into this. 
  
> 	3) Exactly where to artifically draw the line between HW ("language atomic") 
and 
> 	   SW (implimented "in" Pragmatic) 
 
  I think this would be better stated as  
 
	3) Exactly where to artifically draw the line between Implementation  
("language atomic") features and Language features (implimented "in" Pragmatic) 
 
 But the point I think is clear in either case.  


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for Your HP, Epson, Canon or Lexmark
Printer at Myinks.com. Free s/h on orders $50 or more to the US & Canada. http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/sO0ANB/LIdGAA/ySSFAA/W4wwlB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
pragmatic_lang-unsubscribe-hHKSG33TihhbjbujkaE4pw@public.gmane.org

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/