Here it is, first alpha release. If anyone wants to do a Windows/Linux 
port, just say so.

Supports:
while loops, if-else conditionals
objects
functions with parameters
1D arrays
file output
mathematical expressions. No boolean operators, just +-*/. Parentheses 
should work, but are untested. Vectors and scalars work.

To-do for next release:
boolean operators
global variables
general code cleanup, especially the parser
function return values
better documentation/sample files


I just realized I forgot to document the syntax of the CSDL 
interpreter...though it is pretty obvious, "csdl INPUT_FILE". Make sure 
the executable is alongside the "library" directory or all the files are 
in the same directory, or CSDL won't be able to find the library files.
BTW, if you attempt to run the library files, they will print 
information about the file.

Source code (20KB):
homepage.mac.com/chrishuff/csdl_source.tgz

Documentation, example files, library files (12KB):
homepage.mac.com/chrishuff/csdl_dist.tgz

Mac OS X compile (208KB):
homepage.mac.com/chrishuff/csdl_macosx.tgz

-- 
 -- 
Christopher James Huff <chr### [at] maccom>

Post a reply to this message

Christopher James Huff wrote:
> 
> In article <3C47A740.A76C59F7@sw-tech.com>, Deaken <dwy### [at] sw-techcom>
> wrote:
> 
> > <URL:http://www.perl.com/pub/a/language/misc/Artistic.html> is, as
> > usual, my suggestion.
> 
> Looks interesting, I'll take a look at it. I assume I can change
> licenses with later releases if I want...the code is mine, right?

I don't know.  I've seen it done, but I've seen people argue that even the
creator is bound by the license.  My guess is that if you do change
licenses, nobody's going to bother to do anything about it.  If they have a
problem, they'll use an earlier version that has a license that they like. 
It is not something that I've been forced to deal with yet, as most of my
released projects have been very simple and have required neither
maintenance nor feature additions.

Deaken

Post a reply to this message

Christopher James Huff wrote:
> 
> Here it is, first alpha release. If anyone wants to do a Windows/Linux
> port, just say so.
> [...]
> 
> Source code (20KB):
> homepage.mac.com/chrishuff/csdl_source.tgz
> 
> Documentation, example files, library files (12KB):
> homepage.mac.com/chrishuff/csdl_dist.tgz
> 
> Mac OS X compile (208KB):
> homepage.mac.com/chrishuff/csdl_macosx.tgz
> 

Those links don't seem to work, i can get 'homepage.mac.com/chrishuff/'
but none of the 3 files is accessible.

Christoph

-- 
Christoph Hormann <chr### [at] gmxde>
IsoWood include, radiosity tutorial, TransSkin and other 
things on: http://www.schunter.etc.tu-bs.de/~chris/

Post a reply to this message

Deaken <dwy### [at] sw-techcom> writes:
> > Looks interesting, I'll take a look at it. I assume I can change
> > licenses with later releases if I want...the code is mine, right?
> 
> I don't know.  I've seen it done, but I've seen people argue that even the
> creator is bound by the license.

IANAL, but if you are the only contributor to the code base, it's all
under your copyright. So when you do a new release, you're free to
choose another license.

What you can't do is to change the license of an old release, like
this:

  1. Release foobar-0.1 under GNU GPL (thus making it free for all).

  2. Develop foobar-0.2 and release it with some evil proprietary
     license which prohibits people from copying/modifying foobar.

  3. Demand that all use of foobar-0.1 comply with the new license.

As long as you're only doing 1 & 2 there's no problem (well, depending
on your point of view there might be some moral problems, and people
are likely to complain...), but you can't legally do 3.

> My guess is that if you do change licenses, nobody's going to bother
> to do anything about it. If they have a problem, they'll use an
> earlier version that has a license that they like.

I think so too. Though I also think that changing license to something
more prohibitive is going to make some people angry.


My suggestion for licensing is: don't make up a new one yourself,
since a) you would probably need lawyer help to ensure it is good
enough, b) the world already has enough licenses. :-)

Else, I would suggest GNU GPL because choosing that makes it possible to
share code with the rest of the GNU world and avoid license wars with
various parties (that's the pragmatic reason, anyway). And then you
don't have to worry that someone will steal your code and abuse it in
some future commercial product.

-- 
Ole Laursen
http://sunsite.dk/olau/

Post a reply to this message

In article <3C4AA1F5.298177D8@gmx.de>,
 Christoph Hormann <chr### [at] gmxde> wrote:

> Those links don't seem to work, i can get 'homepage.mac.com/chrishuff/'
> but none of the 3 files is accessible.

Oops...these should work:

Source code (20KB):
homepage.mac.com/chrishuff/csdl/csdl_source.tgz

Documentation, example files, library files (12KB):
homepage.mac.com/chrishuff/csdl/csdl_dist.tgz

Mac OS X compile (208KB):
homepage.mac.com/chrishuff/csdl/csdl_macosx.tgz

-- 
 -- 
Christopher James Huff <chr### [at] maccom>

Post a reply to this message

Christopher James Huff scribis news:chrishuff-
AD4### [at] netplexaussieorg:

> 
> Here it is, first alpha release. If anyone wants to do a Windows/Linux 
> port, just say so

I would be intrested in working on a BeOS port (only OS I have a good IDE 
for).
But the files are "not avaliable" at the links you gave.

-- 
Gis poste, Arto.

Post a reply to this message

In article <87w### [at] bachcomposers>,
 Ole Laursen <ola### [at] hardworkingdk> wrote:

>   3. Demand that all use of foobar-0.1 comply with the new license.
> 
> As long as you're only doing 1 & 2 there's no problem (well, depending
> on your point of view there might be some moral problems, and people
> are likely to complain...), but you can't legally do 3.

If I understand things properly, #3 is legal if the old license 
specifically stated that the license could be changed, so anyone using 
the software has warning.


> Else, I would suggest GNU GPL because choosing that makes it possible to
> share code with the rest of the GNU world and avoid license wars with
> various parties (that's the pragmatic reason, anyway). And then you
> don't have to worry that someone will steal your code and abuse it in
> some future commercial product.

But I worry about people *not* using it because it is GPL...some people 
apparently don't like GPL, which is why I'm looking on information about 
licensing.
The artistic license seems interesting...it looks like it would let 
people use it in a program and only have to release the CSDL part of the 
source code. The only other thing is that I want to be sure people know 
they're using CSDL, what it is, and where it came from. I basically 
don't want someone to take the code, maybe make it slightly incompatible 
and release it as something else or use it as the main feature of their 
program and make it look like their work.
If someone is willing to invest the time/money to make a product that 
uses CSDL, I would have nothing against them charging for their product 
or withholding the source code for their work, as long as they make any 
changes/enhancements to CSDL available. People will only buy it if it is 
better than the free stuff, and if the developer makes something better, 
I'll thank them.

-- 
 -- 
Christopher James Huff <chr### [at] maccom>

Post a reply to this message

Arthur Flint scribis
news:Xns### [at] 204213191226: 

> Christopher James Huff scribis news:chrishuff-
> AD4### [at] netplexaussieorg:
> I would be intrested in working on a BeOS port (only OS I have a good
> IDE for).

Found the correct links, thanks.
And congrats! The source compiled first time, no errors.
(a few warnings, but no errors)
So, when you have another release to let us try, let me know.


-- 
Gis poste, Arto.

Post a reply to this message

It compiles fine in Cygwin - now to figure out how to use it :-)

--
duncan gold [TurboPower]
TurboPower: http://www.turbopower.com
Personal: http://www.autowitch.org

"Christopher James Huff" <chr### [at] maccom> wrote in message
news:chr### [at] netplexaussieorg...
> Here it is, first alpha release. If anyone wants to do a Windows/Linux
> port, just say so.
>
> Supports:
> while loops, if-else conditionals
> objects
> functions with parameters
> 1D arrays
> file output
> mathematical expressions. No boolean operators, just +-*/. Parentheses
> should work, but are untested. Vectors and scalars work.
>
> To-do for next release:
> boolean operators
> global variables
> general code cleanup, especially the parser
> function return values
> better documentation/sample files
>
>
> I just realized I forgot to document the syntax of the CSDL
> interpreter...though it is pretty obvious, "csdl INPUT_FILE". Make sure
> the executable is alongside the "library" directory or all the files are
> in the same directory, or CSDL won't be able to find the library files.
> BTW, if you attempt to run the library files, they will print
> information about the file.
>
> Source code (20KB):
> homepage.mac.com/chrishuff/csdl_source.tgz
>
> Documentation, example files, library files (12KB):
> homepage.mac.com/chrishuff/csdl_dist.tgz
>
> Mac OS X compile (208KB):
> homepage.mac.com/chrishuff/csdl_macosx.tgz
>
> --
>  --
> Christopher James Huff <chr### [at] maccom>

Post a reply to this message

In article <3c4cb4df$1@news.povray.org>,
 "autowitch" <aut### [at] autoSPAMwitchorg> wrote:

> It compiles fine in Cygwin - now to figure out how to use it :-)

Well, at least nobody's having trouble compiling it...
Alpha 1 only takes one parameter, the CSDL file to run. Make sure the 
CSDL executable is in the same directory as the demo files and library 
folder. And if you need any help on the language itself, ask...the 
documentation is pretty bad, but the language should be fairly easy for 
anyone who can handle POV-Script or C.

BTW, I just got OpenGL display (using GLUT) working...and I almost have 
function return values working.

-- 
 -- 
Christopher James Huff <chr### [at] maccom>

Post a reply to this message