Re: Pragmatic Requirements Summary : update

> One of the things that killed PL/I- and is killing C++ IMHO- is the
> multiple subsets problem.  A problem Pragmatic is already flirting 
with
> from my view of this maillist.  Here's the thing- PL/I was a really 
huge
> language, large enough that basically no programmer could remember 
the
> whole thing.  So programmers coded in various subsets- unfortunately
> everyone didn't code in the *same* subset.  So you'd get two 
programmers
> working on two projects supposedly in the same language not being 
able to
> understand each other's code because they were coding, and knew, 
disjoint
> subsets.  Or worse yet two programmers on the *same* project 
working in 
> disjoint subsets and not being able to maintain each others code 
> (increasing the truck factor of the project).
> 
> Brian

 This doesnt really seam to be a problem for lisp (the only other 
langauge that I know of with this kind of extensability). One of our 
main goals is consistancy. I hope we can keep this, then if two 
programmers have a problem it will just be a style issue. This 
problem is faced all the time. There are a few other things we can 
probably do to mitigate this.


------------------------ 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/