<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/scriptlang/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/scriptlang/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Thu, 28 Aug 2008 20:38:44 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/scriptlang/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>Some general ideas</title><link>https://sourceforge.net/p/scriptlang/feature-requests/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Here are some general ideas about the language itself I am going to implement in the nearby future (order is mainly arbitrary):&lt;/p&gt;
&lt;p&gt;- multiple assignments, should assignments be makeable inside the expressions or not? what about the values to be used inside the expression? that is a real problem now&lt;br /&gt;
- 'lambda functions', predefined in the language as an 'expression object', which can be 'call' as a normal function&lt;br /&gt;
- possibility to initialize function parameters, before its call, by name, eg.: func(12, param = "string", "other parameter")&lt;br /&gt;
- possibility to define syntax on runtime of the script, using the 'define-as' keywords eg.:&lt;br /&gt;
define if (condition) do (expression) as ((condition) and (expression))&lt;br /&gt;
unfortunately, it is not known yet how exactly it will be implemented, maybe with some kind of regular expression matching, instead of simple preproceesor 9I am waiting for suggestions)&lt;br /&gt;
-  some string operators, such as 'concatenation', and multiplying strings by numbers, maybe 'format operator' (as it is in Python)&lt;br /&gt;
- long integers - numbers of unlimited length (also taken from Python)&lt;br /&gt;
- exceptions (maybe in the future?)&lt;br /&gt;
- classes, should they be predefined in language itself or defined in 'define-as' style? (both of this is not so difficult, I think)&lt;br /&gt;
- arrays, (implemented as hash tables of course)&lt;br /&gt;
- functions as an objects (this is forced by lamda functions)&lt;br /&gt;
- fully objected-oriented language, is it not to early to think about it? ;)&lt;/p&gt;
&lt;p&gt;That were some indeas I come up with and wrote here, but I do not know now what exactly will be fully implemented. I am waiting for Your reply,&lt;/p&gt;
&lt;p&gt;thanks&lt;/p&gt;
&lt;p&gt;Dave&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dawid Fatyga</dc:creator><pubDate>Thu, 28 Aug 2008 20:38:44 -0000</pubDate><guid>https://sourceforge.netde29a52f5f9c17eebc12aa68d3015b7b1426c7c0</guid></item></channel></rss>