Skip to main content ↑ ↓
Topic: neoSphere 5.10.1 (Read 8506171 times) previous topic - next topic
0 Members and 13 Guests are viewing this topic.

Re: minisphere 4.2.0

Reply #1306 –
@Eggbert: Just double-checked, I was right.  Your "4.2.0" AUR package is actually using sources for 4.1.1.  You might want to fix that. ;)

Re: minisphere 4.2.0

Reply #1308 –
Huh.  Maybe the AUR site is bugged or something then.  See the screenshot below, under Sources it lists the tarball for 4.1.1:
https://drive.google.com/open?id=0BxPKLRqQOUSNRGFGWGw0OEJ4bDg

If I download that tarball, it is indeed the 4.1.1 sources.  Weird.

Edit: The .SRCINFO you linked points to the 4.1.1 tarball.

Re: minisphere 4.2.1

Reply #1310 –
minisphere 4.2.1 renames a few APIs for consistency.  Notably, the "terminal" module is now called simply "term"

Re: minisphere 4.2.1

Reply #1312 –
You don't have to, it's not an important update.  No bug fixes or anything like that.

Re: minisphere 4.2.2

Reply #1314 –
minisphere 4.2.2 fixes the "struct" and "logger" modules, which stopped working due to the recent changes to the FileStream object.

@Eggbert: You should update the AUR package, since the broken modules in question are part of the standard library (miniRT).

Re: minisphere 4.2.2

Reply #1316 –
Yeah, there's a clang build in minisphere's Travis test.  Most of the warnings are because minisphere does this a lot:

Code: (c) [Select]

if (something = something_new(...)) {
    // ...
}


Clang complains because I'm doing assignment directly in the conditional but it thinks I want to do comparison instead.  I could make the warnings go away by adding an extra set of parentheses around the assignment, but I'm too lazy. :P

Re: minisphere 4.2.2

Reply #1317 –
See here:
https://github.com/svaarala/duktape/pull/987

I have a Duktape patch in the works to add support for the new JS exponentiation operator (x**y), hopefully that'll make it into minisphere soon. :D