This PR removes the copyleft code I could find and tries to use permissive alternatives where possible.

• Added three new vendored libraries in thirdparty/, which are distributed given their individual licensing conditions as seen in the license header and README.md in each of their seperate respective subdirectories, to accomplish compilation using Visual Studio:

  • asprintf
  • gettimeofday
  • strsep

• Removed support for termios, use HAVE_TERMIOS to signal termios support.

• Use configure_file() in CMakeLists.txt to generate config.h from config.h.in.

• Introduced several new configuration variables to config.h.

• Use BSD-licensed getopt instead.

• Use system-provided unistd.h and getopt.h if possible, i.e. on *BSDs, Linux and macOS, rather than the included versions.

• Add own dirname and basename implementation using _splitpath_s.

GOTCHAS

• Ctrl-C is no longer handled on Windows. The POSIX signal SIGINT is not supported by default on Windows; are handled differently and are handled on a different thread, and support for this must be added later.

• Most #include directives need significant clean-up, because there is a lot of redundancy.

• A pre-compiled header should be used in place of #include <Windows.h> and so on as there are a large number of subsequent dependencies of that header, which slows compilation down; also, this is considered good practice on Windows.

• credits() in the REPL should present the licenses for thirdparty libraries if they are linked in.

Fixes issue #47.

Hello,

We want to create a programming language for professional, personal and utility needs. We want to base ourselves on your language, which we find very interesting in its simplicity and speed. Can we fork your project? Or take over the project for free?

Cordially, Zuygui

Windows 10 21H1 cmake version 3.21.4 VSC 2019 - 16.11.6 / MSVC v142 / kit SDK Windows 10 (10.0.19041.0)

install Cygwin/mingw64 if necessary

try this script:

import os

echo '\x1B[31m' + ' Hello foo: before c++/\msys64 use ' + '\x1B[0m'
os.exec('C:\\msys64\\mingw64\\bin\\c++ --version')
echo '\x1B[32m' + ' Hello foo:  after c++/\msys64 use ' + '\x1B[0m'

echo ""
echo '\x1B[31m' + ' Hello foo: before c++/cygwin use ' + '\x1B[0m'
os.exec('C:\\cygwin64\\bin\\c++ --version')
echo '\x1B[32m' + ' Hello foo:  after c++/cygwin use ' + '\x1B[0m'

result:

Hello foo: before c++/\msys64 use 
Hello foo:  after c++/\msys64 use 

Hello foo: before c++/cygwin use 
←[32m Hello foo:  after c++/cygwin use ←[0m

P.S. easier to test the 'bug': download wgrib2.exe and all cygwin dll at: https://ftp.cpc.ncep.noaa.gov/wd51we/wgrib2/Windows10/v3.0.2/

echo '\x1B[31m' + ' Hello foo: before wgrib2 use ' + '\x1B[0m'
os.exec('path_to_wgrib2\\wgrib2 --version')
echo '\x1B[32m' + ' Hello foo:  after wgrib2 use ' + '\x1B[0m'

OS: Windows 10 Professional version: 21H1 Blade version : 0.0.6

Run the following script,

var str_len = 1500
#str_len = 200
var file_id = file('foo')
file_id = file('bar')
# Loop for creating 'str' string
var str = ''
iter var idx = 0; idx < str_len; idx++ {
    str += '1'
}
echo 'End of iter loop'

Result: the last line is not executed because the loop that creates the string stops before the end and interrupts the script.

If you either uncomment line 2 # str_len = 200 (the string length is reduced to 200 characters) or comment line 4 file_id = file('bar') (file_id is no longer overwrited), End of iter loop is displayed as expected.

Describe the bug

A clear and concise description of what the bug is.

To Reproduce

Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior

A clear and concise description of what you expected to happen.

Screenshots

If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context

Add any other context about the problem here.

Windows 10 / 21H1 Blade 0.0.6 (latest)

The following script that creates a list of 'n' numbers breaks if 'n' is above 406

 def create_list(list_len) {
     var list = []
     echo "Trying to create a ${list_len}-elements list"
	     iter var j = 0; j < list_len; j++ {
		     list += [j]
	     }
     echo "      list content: " + list[0] + ", " + list[1] + " ... " + list[-2] + ", " + list[-1]
}
 
 var n = 500
 echo ""
 create_list(n);

echo "\nEnd of script"

Result if 'n' equals 500:

 Trying to create a 500-elements list

Result if 'n' equals 400:

 Trying to create a 400-elements list
           list content: 0, 1 ... 398, 399

 End of script

Often times what gets me and many other people to not look further into projects, is the lack of very minimal examples. I think the README should contain a tiny example, so that people can get a feel for the language right away. Since the language is very small, it doesn't really make that much sense to have a hello world example.

I propose something like:

def sum(numbers) {
    var result = 0

    for num in number {
        result += num
    }

    print(result)
}

sum([1, 2, 3, 4]) # this will print "10"

This presents the developer with information about:

• functions
  • defining functions
  • calling functions
  • function arguments
• variables
• for loops
• assignment
• printing
• arrays
• single-line comments

blade_termios.h has a file header which shows that it has been originally licensed under GPL v3.

This file must be removed to keep blade under the permissive conditions of the MIT license.

I followed the instructions for installation, however once I get to curl the repo, I get an error 46% into the make saying the following:

[ 46%] Built target linenoise
cc: fatal error: Killed signal terminated program cc1
compilation terminated.
gmake[2]: *** [thirdparty/pcre2/CMakeFiles/pcre2.dir/build.make:251: thirdparty/pcre2/CMakeFiles/pcre2.dir/pcre2_match.c.o] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:351: thirdparty/pcre2/CMakeFiles/pcre2.dir/all] Error 2
gmake: *** [Makefile:114: all] Error 2
cp: cannot create directory '/home/root/.blade': No such file or directory
mv: cannot stat '/home/root/.blade': No such file or directory
Linking Blade...

Desktop:

• OS: Raspbian / Raspberry Pi OS
• Version: 11 (Bullseye)

Is your feature request related to a problem? Please describe.

print(10) in the REPL outputs 10nil It does not look nice when printing, that it is followed by nil.

Describe the solution you'd like

print(10) should print 10 and not include nil.

This can be fixed by changing: https://github.com/blade-lang/blade/blob/main/src/vm.c#L1549-L1553

Currently this is the code:

if (vm->is_repl) {
  echo_value(peek(vm, 0));
} else {
  print_value(peek(vm, 0));
}

I propose:

if (vm->is_repl) {
  // maybe have a variable to avoid peeking twice
  if (!IS_NIL(peek(vm, 0))) {
    echo_value(peek(vm, 0));
  }
} else {
  print_value(peek(vm, 0));
}

I'm curious as to why this is a thing. Is this a bug or is it for something like debugging? If wanted I can go ahead and PR this.

Currently comments are being made like so:

# Hello World

/* 
Hello
There
World 
*/

This to me does not make sense. Not only is this inconsistent with languages like JS, C, Python and a whole bunch of other languages. But it's also a bit harder to remember. My proposal is to use // comment instead as it makes switching to Blade easier. It's easier to remember, not only because of other languages, but also because one character less is used.

If this isn't going to be changed to // that is fine, but I do at least propose some more consistency between single line and multiline comments. In JS, C and many more languages this is the / character, since it is used for both single-line and multiline. In Lua this is --, etc...

Long time since I've been here, but I've been following the project closely. One thing that I have not been a fan of, is the exception with echo not requiring braces. It's inconsistent and I'm not quite sure I understand the purpose of it?

Hi All,

The current Blade icon and logo are not very professional or attractive. Using this issue to request help from designers to help create one that looks cool and professional.

Thanks in advance.

Regards

Is your feature request related to a problem? Please describe.

As it stands, Blade classes are first class and can be used in almost anything including iterables, values and more. It will greatly increase consistency to have Blade classes support operator overloading from classes.

Proposed Solution

Since today, Blade classes can become iterators by implementing the @iter and @itern decorators, Blade can employ decorators for operator overloading support.

E.g.

class A {
    @+(a2) {
        return self.value + a2.value
    }
}

var a1 = A()
a1.value = 5

var a2 = A()
a2.value = 7

echo a1 + a2

The above sample code should print 12 to terminal.

Alternative Solution

As an alternative, we could use a keyword operator.

For example:

class A {
    operator + {
        return self.value + __arg__.value
    }
}

var a1 = A()
a1.value = 5

var a2 = A()
a2.value = 7

echo a1 + a2

This will at best require an extra conditionally valid keyword __arg__.