• Raju Renjit. G (1/1) Jun 22 2009 This paper gives a method to incorporate table like data types into any ...
• Daniel Keep (5/6) Jun 22 2009 osal the actions for each transitions in the diagrams can be written els...
• BLS (4/5) Jun 23 2009 osal the actions for each transitions in the diagrams can be written els...

Raju Renjit. G <rajurenjitgrover yahoo.com> writes:

This paper gives a method to incorporate table like data types into any
programming languages (any language that does not have structs or classes, for
example fortran). When such a thing is done it is very easy to incorporate SQL
directly into the language. I mean I do not use any specialized classes to
implement this (for the time being I do not have any other name for it. So I
use the name LINQ.) So this proposal can be used with int, float, etc. LINQ to
SQL is also done without any specialized classes. The title of that sub section
is ``Passing SQL statements without quotes." It is just a trick and there is
nothing complicated in it. That would make it similar to writing SQL statements
on the interface of a database. And the proposal is not specific to any
database like Oracle or MySQL or SQL Server. The next section contains a
proposal for  incorporating state diagrams as a feature of an Object oriented
PL in an object oriented way except for polymorphism. In the  proposal the
actions for each transitions in the diagrams can be written elsewhere. So
something can be used to encapsulate only the underlying graph and the
transitions can be written elsewhere (It is almost like drawing the diagram on
paper. But a program cannot use pictures. So it is almost like drawing a
graph.). The next section contains a proposal for incorporating templating as
feature of a programming language in an object oriented way. If this is
incorporated into a language, then compilation will become: First execute an
object oriented program by the complier which in turn generates the actual
program to be complied (well, all these done programatically and not retrieved
from a database). So this will enable code reuse. The next section contains
something like the generalized switch statement, array and list
transformations, temporary expressions, the match loop etc. They are not
complex. Please visit http://arxiv.org/abs/cs/0504025 . Also you will find an
elegant way to have operator overloading in it. And also a new framework for
object oriented programming languages.

Daniel Keep <daniel.keep.lists gmail.com> writes:

Raju Renjit. G wrote:
 This paper gives a method to incorporate table like data types into any
programming languages (any language that does not have structs or classes, for
example fortran). When such a thing is done it is very easy to incorporate SQL
directly into the language. I mean I do not use any specialized classes to
implement this (for the time being I do not have any other name for it. So I
use the name LINQ.) So this proposal can be used with int, float, etc. LINQ to
SQL is also done without any specialized classes. The title of that sub section
is ``Passing SQL statements without quotes." It is just a trick and there is
nothing complicated in it. That would make it similar to writing SQL statements
on the interface of a database. And the proposal is not specific to any
database like Oracle or MySQL or SQL Server. The next section contains a
proposal for  incorporating state diagrams as a feature of an Object oriented
PL in an object oriented way except for polymorphism. In the  prop

osal the actions for each transitions in the diagrams can be written elsewhere.
So something can be used to encapsulate only the underlying graph and the
transitions can be written elsewhere (It is almost like drawing the diagram on
paper. But a program cannot use pictures. So it is almost like drawing a
graph.). The next section contains a proposal for incorporating templating as
feature of a programming language in an object oriented way. If this is
incorporated into a language, then compilation will become: First execute an
object oriented program by the complier which in turn generates the actual
program to be complied (well, all these done programatically and not retrieved
from a database). So this will enable code reuse. The next section contains
something like the generalized switch statement, array and list
transformations, temporary expressions, the match loop etc. They are not
complex. Please visit http://arxiv.org/abs/cs/0504025 . Also you will find an
elegant way 
to have operator overloading in it. And also a new framework for object
oriented programming languages.

Good grief.

http://en.wikipedia.org/wiki/Paragraph

BLS <windevguy hotmail.de> writes:

Raju Renjit. G wrote:
 This paper gives a method to incorporate table like data types into any
programming languages (any language that does not have structs or classes, for
example fortran). When such a thing is done it is very easy to incorporate SQL
directly into the language. I mean I do not use any specialized classes to
implement this (for the time being I do not have any other name for it. So I
use the name LINQ.) So this proposal can be used with int, float, etc. LINQ to
SQL is also done without any specialized classes. The title of that sub section
is ``Passing SQL statements without quotes." It is just a trick and there is
nothing complicated in it. That would make it similar to writing SQL statements
on the interface of a database. And the proposal is not specific to any
database like Oracle or MySQL or SQL Server. The next section contains a
proposal for  incorporating state diagrams as a feature of an Object oriented
PL in an object oriented way except for polymorphism. In the  prop

osal the actions for each transitions in the diagrams can be written elsewhere.
So something can be used to encapsulate only the underlying graph and the
transitions can be written elsewhere (It is almost like drawing the diagram on
paper. But a program cannot use pictures. So it is almost like drawing a
graph.). The next section contains a proposal for incorporating templating as
feature of a programming language in an object oriented way. If this is
incorporated into a language, then compilation will become: First execute an
object oriented program by the complier which in turn generates the actual
program to be complied (well, all these done programatically and not retrieved
from a database). So this will enable code reuse. The next section contains
something like the generalized switch statement, array and list
transformations, temporary expressions, the match loop etc. They are not
complex. Please visit http://arxiv.org/abs/cs/0504025 . Also you will find an
elegant way 
to have operator overloading in it. And also a new framework for object
oriented programming languages.

What does that mean for D ?