Re: the relational model of data objects *and* program objects
From: Kenneth Downs <knode.wants.this_at_see.sigblock>
Date: Fri, 15 Apr 2005 14:44:28 -0400
Message-Id: <dne5j2-tic.ln1_at_pluto.downsfam.net>
> them,
>
> PMFJI. This may have been covered already elsewhere in the discussion.
> If so, my apologies.
>
>
> I'm playing around with the idea of a programming language that combines
> the functionality of traditional programming,
> library function invocation, and data exchange with database servers
> and/or
> user interface servers. In this concept,
> SQL becomes the OUTPUT of a compiler, instead of the input to a compiler.
>
> That is, you have a language in which code "makes sense", and is
> unified.
> The compiler figures out which things should be coded to run on, say, a
> Java Virtual Machine, which things should be resolved by library function
> calls, and which things should be recoded as SQL style exchanges with
> external servers.
>
> I know this isn't exactly the direction you are going in. But maybe
> there's a useful synthesis.
Date: Fri, 15 Apr 2005 14:44:28 -0400
Message-Id: <dne5j2-tic.ln1_at_pluto.downsfam.net>
David Cressey wrote:
>
> "Kenneth Downs" <knode.wants.this_at_see.sigblock> wrote in message
> news:60l3j2-g8s.ln1_at_pluto.downsfam.net...
>
>
>> This is why the One True Data Dictionary must exist outside of all of
> them,
>> and be used to implement all of them. If the spec is both >> machine-readable and human-readable, mores the better.
>
> PMFJI. This may have been covered already elsewhere in the discussion.
> If so, my apologies.
>
>
> I'm playing around with the idea of a programming language that combines
> the functionality of traditional programming,
> library function invocation, and data exchange with database servers
> and/or
> user interface servers. In this concept,
> SQL becomes the OUTPUT of a compiler, instead of the input to a compiler.
>
> That is, you have a language in which code "makes sense", and is
> unified.
> The compiler figures out which things should be coded to run on, say, a
> Java Virtual Machine, which things should be resolved by library function
> calls, and which things should be recoded as SQL style exchanges with
> external servers.
>
> I know this isn't exactly the direction you are going in. But maybe
> there's a useful synthesis.
This is not the implementation direction I've gone in, but it is very close to the original intent, something that knows where to put things based on a holistic specification.
I would have to ask what you mean by "language". Ours is purely declarative, meaning it is actually data dressed up for readability. It is a "language" only if CSS is a language.
-- Kenneth Downs Secure Data Software, Inc. (Ken)nneth_at_(Sec)ure(Dat)a(.com)Received on Fri Apr 15 2005 - 20:44:28 CEST