The lunkheads who keep thinking they will have to edit XML should get a clue. You can keep using the syntax you are familiar with if you want. On the other hand, all sorts of new features can be added as decorators once the program is represented internally as a tree structure (and stored as XML).
Read Knuth's "Literate Programming." Then imagine the feature built into your development environment, not part of a preprocessing chain.
Design your objects using UML and view them with UML or as your favorite conventional language. (This is currently available under the labels "forward-" and "reverse-engineering," but these are really different viewpoints of the same program, not separate files that have to be kept in sync somehow.)
Though it's been inactive for some time, you might want to look at the eXtenDE project on SourceForge, http://extende.sourceforge.net/
pongo, patents allow the patent holder to prevent the end user from using the patented invention. It is a violation to use a patented invention without a license from the patent holder.
Note that this is different from how copyrights work. Once you have a copy of a copyrighted work, you have (at least in the United States) certain "fair use" rights.
So, in theory at least, a patent holder can sue an end user to prevent him/her from using the patented invention without a license, and the patent holder can obtain an injunction from a court to forbid use of the patented invention by an unlicensed end user.
Slashdot Mirror
The lunkheads who keep thinking they will have to edit XML should get a clue. You can keep using the syntax you are familiar with if you want. On the other hand, all sorts of new features can be added as decorators once the program is represented internally as a tree structure (and stored as XML).
Read Knuth's "Literate Programming." Then imagine the feature built into your development environment, not part of a preprocessing chain.
Design your objects using UML and view them with UML or as your favorite conventional language. (This is currently available under the labels "forward-" and "reverse-engineering," but these are really different viewpoints of the same program, not separate files that have to be kept in sync somehow.)
Though it's been inactive for some time, you might want to look at the eXtenDE project on SourceForge, http://extende.sourceforge.net/
Note that this is different from how copyrights work. Once you have a copy of a copyrighted work, you have (at least in the United States) certain "fair use" rights.
So, in theory at least, a patent holder can sue an end user to prevent him/her from using the patented invention without a license, and the patent holder can obtain an injunction from a court to forbid use of the patented invention by an unlicensed end user.