eScript is dynamic (with struct members;) weak typed DSL when it comes to variables. It would be less stressful to newcomers if compiler wouldn't allow blank variable declaration i.e.var smthing not followed by an immediate assignment operator.

var something := struct{};

is important because it ...

I agree that readability counts and you probably shouldn't confuse your readers with what I said.


As for assignment the need to push a combo of 3 keys to type := instead of 1 key for =
is annoying. My guess is that Eric Swanson was fond of Pascal syntax much thus the syntax. Its has some history ...

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

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

I think its brilliant that you made this coding style. I would probably succumb to using one of the pre-existing code convention (something akin to PEP8), yet a fresh look yields nicer things!

Note: spells that are cast via conventional means (like a spellbook) would also have spellId argument ...

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 ...

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

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 ...

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 ...

Yes, std::rotate seems to be doing the trick with a bit of tinkering.

I don't suppose I'll do another patch though. The mechanics got exceedingly complicated
since you moved to github, and you seem to know your magic well without me.


case MTH_CYCLE:
if (name_arr.empty())
{
int shift_by ...

Thats a terrific suggestion, thanks Turley.

array.cycle() will move array backwards or forwards in-place as it were a conveyor belt.

{1, 2, 3}.cycle()

Will make it:
{3, 1, 2}

Accepts a negative value as a shift to move different direction.
* Currently only shift by 1 element is supported.

The performance probably is horrible like O( 2*N ...

Not much into BOOST yet, but I study it.
The thing is that you have to incorporate the patch somehow.
The previous version has a bug.

I shall use your suggestion about size_t for the next submissions.
I don't even have 64bit version thus these things happen.

* Now actually faster than string concatenation in eScript
* Fixes a bug where {:d} formating could cause an arbitrary number shown instead of a real value
* tag errors are slightly more intuitive and compact.

SubStrReplace (str, replace_with, start, length:=0);

doesn't work if start + length >= the length of the string
which should be perfectly legal for POL since its indexations are 1-based

such that:

var myString := "Hello, World!" ;
SubStrReplace (myString , "Hell!" , 7, length:=6);

>> Would ...

em functions are executed by the core thus aren't included into .ecl. I believe core does a map lookup for every call to a module function with a separate map per module. I am not sure if using additonal modules incur any performance penalty. In theory UO.EM has substantially bigger number of ...

I wonder if bundling all functions in a single em would be substantially slower. I'd probably try to push these to a single hash-map.

Hey Xeon,
Nice to see people are still active on Zulu scene.
I think true multi-core isn't an easy feat to accomplish with reference counting.
To be honest I don't know much about what happens under the hood but it might require
an exquisite locking mechanism.
There is also other nice language ...

I want to contribute my stable POL099 binaries.

- Based on the latest beta core release (rev. 180) that is proven to be VERY STABLE.
- Back-porting the majority of SVN fixes: MySQL/XML/Numerous memory leaks are fixed
- Some additional functionality added by me (see core-backport.txt)
- added some ...

Fixes an old bug when .hp member rolls over for negative values as referred by RusseL:
http://forums.polserver.com/viewtopic.p ... 187#p20187

Use at your own discretion.

I use EmEditor . It has code completion as well as easy customizable code highlighting, and an extensive snippets support. It also allows you to compile scripts not leaving the IDE as well. No highlighting glitches or troubles with changing fonts.
I tried UltraEdit , but its a bit heavy for the ...

What with all this positive attitude all of a sudden=) Anyway its done now.

I think I'll be using python syntax very close to what Yukiko has suggested. I also have an idea for extending arrays API with 2 more calls.

array.reject_by(membername, membervalue) : new Array
array.reject_by(membername) : new Array
array.collect_by(membername) : new Array
array.collect_by ...

Assuming you are using new gumps by Austin. Feed your text_entries to a dictionary :


var gump := GFCreateGump(10, 40, 200, 240);
GFResizePic(gump, 0, 0, 2600, 0, 0 ); // just a background

var text_etries := dictionary {};

GFGumpPic( gump, x, y-1, 0x98d ); // medium sized background
text ...

I shall look into it, but I think I'd replicate some preexisting syntax like of a .Net or something, perhaps Python's.