I am working on a new new POLocre99 fork, base off the latest Git version.
It has several enhancements official version that didn't make it to POL:

- Numerous addition ways to work with arrays and strings:
array shuffling, case insensitive String compare, bulk array filtering.
- Unicode problem is addressed in most cases
- Web server supports several additional headers

- StrFormatTime is always in "C" locale
- FormatRealToString expects min decimal points instead of number of digits and never produces any abnormalities.
Among many others such as tile "spoofing" bug is fixed (for a long time).

Its not really difficult to make it backwards compatible with POL095 or even POL092
I wonder if anyone is interested in such compatibility is actually demanded by some individuals that are unable to leap forward from their old script bases.

--cheers

Wow, very interesting!
Andenixa, did you realise your sweet FX functions in it?)

Can you show some cut of the scripts code, what does it look like? Are there many changes with usual?

To be frank I am not quite following with sweetFx thing for which I apologize.
Perhaps you could elaborate on that.
There is hefty of changes from the original git core which make the scripting routine
itself differ tremendously as I always aim for rapid development with less effort (for scripters).
It may also allow to have scripts in your current locale, i.e. you can use your native tongue for variable and function names.
I am currently work to make Unicode more adaptable in a way that it will auto-detect the native encoding. I would switch to utf-8 everywhere in String object, however POL team has plenty of places where they use char* type thus utf-8 would probably make the core go apesh*t. However I do use utf-8 for MySQL.
Generally most of the things in core are easier than they appear. I can't say I don't have time for it neither, but I lack certain audience who'd demand some game related changes as I only fill in the blanks where its due.
Not for the sake of writing the code itself.
And it ain't no beta stage neither. The changes are pretty mature and had gone through vigorous testings.
I tried to push it through the official channels, but things rarely get accepted in the mainstream core anymore.

andenixa wrote: ↑Sat Jul 15, 2017 7:40 pm I tried to push it through the official channels, but things rarely get accepted in the mainstream core anymore.

Sparetime is always a problem
I personally would like to see a pull request so we can take a look and merge it.

Thanks for the note Turley. I shall try that.
Its became increasingly hard to catch you at IRC last I checked that was probably like 3 years ago.
IS work killing you?

--cheers

I would say the biggest time killer is my 1.5 year old little girl
And yes I would say in IRC your chances are almost 0%

Shame on you Turley for letting something as trivial as your little girl get in the way of POL! tisk, tisk.

But seriously, take good care of your future POL developer. Have you started teaching her C yet?

It is good to see you around the forums again.

Good to know, just to say that one POL to track is enough
Given that POL is niche stuff, I would suggest you to stick with "official" POL and submit patches, or get into the core developer teams, to not disperse coding power around

It would be nice to have a link to the source so people interested can peek on it.

That's how open source works.

There is a source:

https://bitbucket.org/ivanovar-08/polcore_git

Its not ready for public consumption I guess though I try to make it so.
It compiles and everything, but its kind of a transition build and I do a lot
of experimental stuff that could make the more CPU demanding (depending on usage scenario).
Some people have reported crashes under Debian x64 Linuxes at libconv.so
I was not able to replicate or isolate the issue.

I don't think its possible to get into the coding team. I tried back at 2011-2014 when I had lots of time on my hands. Didn't happen.

--cheers

Mmmh I remember a few patches you submitted but no request of beeing a part of the dev team. But that was the time I was pretty much focused with my limited time to code something. So if I lost/ignored that I'm sorry. But I hope it was a public mail/request so we can also blame nando and the others to ignore you
If you are still interested join the discord server and we can talk about the needed steps.

There is no one to blame. Austin was the one who denied my request at the time and he might have had his reasons for that. It would be great to get on board!
I shall check hard if I can balance my free-time "checkbook" (guess you don't need an idling member).

Thank you for the invitation,

--cheers

We all more or less idle around :p
If you are to active we only feel bad so beeing a core Dev does not mean you need to commit every week, what is even more important is to complain about the old school parts of the core and discuss rewrites which are way to big to ever be started :p

Almost forget:
Once in the while it's important to commit some new senseless methods or members for escript to keep yukiko happy :p

Turley wrote: ↑Sun Aug 27, 2017 10:16 am Almost forget:
Once in the while it's important to commit some new senseless methods or members for escript to keep yukiko happy :p

Everything if only to keep yuki子 happy;) We may even invent methods that do a printout on which methods are absolutely senseless :p

Hey! When have I ever asked for a senseless method? Don't answer that!!!
But you could implement the DWIM compiler directive. It would force the compiler to Do What I Meant to do and not what the script says to do.
Turley is correct about the devs. They gripe about the older parts of the code and talk about fixing it then decide it would be too hard.
But seriously, I think I speak for all the devs when I say we would be happy if you joined the team.