The Artima Developer Community
Sponsored Link

.NET Buzz Forum
More thoughts around Code Generation and Extensible Programming Systems

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Scott Hanselman

Posts: 1031
Nickname: glucopilot
Registered: Aug, 2003

Scott Hanselman is the Chief Architect at Corillian Corporation and the Microsoft RD for Oregon.
More thoughts around Code Generation and Extensible Programming Systems Posted: Jun 9, 2004 10:21 AM
Reply to this message Reply

This post originated from an RSS feed registered with .NET Buzz by Scott Hanselman.
Original Post: More thoughts around Code Generation and Extensible Programming Systems
Feed Title: Scott Hanselman's ComputerZen.com
Feed URL: http://radio-weblogs.com/0106747/rss.xml
Feed Description: Scott Hanselman's ComputerZen.com is a .NET/WebServices/XML Weblog. I offer details of obscurities (internals of ASP.NET, WebServices, XML, etc) and best practices from real world scenarios.
Latest .NET Buzz Posts
Latest .NET Buzz Posts by Scott Hanselman
Latest Posts From Scott Hanselman's ComputerZen.com

Advertisement

Got forwarded an interesting link from Dr. Gregory Wilson at the University of Toronto.  He's an editor at Dr. Dobbs as well, and has an article up called Extensible Programming for the 21st Century that touches on many of the topics I've been concerned with lately. 

He makes some interesting assertions, starting with:

This article argues that next-generation programming systems will accomplish this by combining three specific technologies:

  • compilers, linkers, debuggers, and other tools will be plugin frameworks, rather than monolithic applications;
  • programmers will be able to extend the syntax of programming languages; and
  • programs will be stored as XML documents, so that programmers can represent and process data and meta-data uniformly.

Ok, #1 no problem, we arguable have this with the CLR's model, while #2 is a little different.  I assume he means actual keyword syntax, as opposed to the way we "changed" programming languages in C with preprocessors and inline functions.  Of course, LISP and Schema use macros to the point where one can't tell where the language starts or ends.  Additionally, custom language constructs like the "using" statement in C# that "expands" into a try/finally use of the IDisposable pattern extend the language within a specific context - so I'll buy #2 also.  I used to think that Number 3 is more of a stretch, but then you've got XAML sneaking up on us as well (not to mention our own foray into XML and CodeGen).

I supposed the question I am left with after reading his article is - hasn't all this already happened?

Read: More thoughts around Code Generation and Extensible Programming Systems

Topic: How an idea becomes a C# language feature? Previous Topic   Next Topic Topic: Code Complete, 2nd Edition

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use