dockimbel on master
FIX: bulk SET changes are ignor… FIX: out-of-bound UNSET pre-che… TESTS: test suite for CHANGED r… and 1 more (compare)
dockimbel on master
TESTS: add regression test for … Merge branch 'master' into issu… Merge pull request #4696 from 9… (compare)
dockimbel on master
TESTS: add regression test for … Merge pull request #4695 from 9… (compare)
dockimbel on master
TESTS: add regression test for … Merge pull request #4694 from 9… (compare)
libcurlrequires 16 bytes alignment as it uses SSE instructions. It doesn't always causes crash because sometimes the stack happens to be 16 bytes aligned. I think that's why we have at least 2 tickets about it but I cannot reproduce it.
--== Red 0.6.3 ==-- Type HELP for starting information. >> probe now/time stats 13:37:40 == 3399680 >> probe now/time stats 13:37:41 == 3399680 >> probe now/time stats 13:37:42 == 3399680 >> probe now/time stats 13:37:43 == 3399680 >> probe now/time stats 13:37:43 == 3399680 >> probe now/time stats 13:37:44 == 3399680
Red for Windows version 0.6.3 built 26-Mar-2018/1:14:22+02:00.
recycle, but not as drastically as in @nedzadarek case.
--== Red 0.6.3 ==-- Type HELP for starting information. >> probe now/time stats 23:15:09 == 2463068 >> probe now/time stats 23:15:11 == 2465536 >> probe now/time stats 23:15:13 == 2468356 >> probe now/time stats 23:15:14 == 2471680 >> probe now/time stats 23:15:15 == 2475508 >> probe now/time stats 23:15:16 == 2479840 >> probe now/time stats 23:15:17 == 2484676 >> probe now/time stats 23:15:18 == 2490016 >> probe now/time stats 23:15:18 == 2495860 >> probe now/time stats 23:15:19 == 2502208 >> probe now/time stats 23:15:20 == 2509060 >> system/build == make object! [ date: 2-Oct-2018/23:14:00+03:00
Okay, everybody! Hope your week is off to a great start! I’d like to thank everyone who responded on-list and off to our questions about yourselves. It's a big help for us, because our goal is to make Red as responsive to your needs as possible. While our due date has passed, you can still send your responses to myself or Gregg privately, and I can add them to our sheets. Our set of questions is appended at the end of this update.
Last week in Red saw contributions from across the spectrum from our heavy hitters. In the midst of gearing up for Ethereum’s Devcon 4 in Prague at the end of October, a diverse number of elements are getting worked on:
@qxtie has added Trezor hardware support to the Red Wallet, in addition to the LedgerX hardware, a goodly chunk of work (see: here) as well as the ability to set up a batch of payments.
There is also new support provided for homebrew APIs for fetching balances, for those who DIY. This is still work in progress, but we’ll write it up in detail when it’s ready.
There has also been a lot of work done to add bitcoin support to the wallet, but bitcoin is messy, and we're still looking at whether it's worth including.
In Red specifically, a number of modifications have been made to work around MacOS issues, and extra attention paid to the GC/recycle facility, with fixes and tests from @dockimbel, @PeterWAWood, and @qxtie.
As for new issues, some GUI aberrations have been observed, related to the appearance of checkboxes and buttons. While not blue-screen-of-death critical, they have been flagged as bugs and will be addressed. Cross platform GUIs are hard, which is why so few do them.
Also, more cool demos from @toomasv, who built a protototype interactive GUI editor, and demoed it building a little live-code app.
In the community, some great discussion has been transpiring around the issue of Red’s mission: is it, or should it be, for “everyone” as our public-facing documentation states? And many folks have stated that while they generally don’t pay for software themselves, they WOULD be willing to shell out for a comprehensive book volume on the subject of Red. Tell us what you think!
If you will be at Ethereum DevCon 4, or in the general area of Prague during the first week of November, hit up @GreggIrwin or @dockimbel; they will be hosting a small, informal RedCon after the main Ethereum event. We’d love for you to be there.
Those community questions, again:
Do you consider yourself a programmer?
Do you consider yourself a software engineer?
Do you solve business problems with software?
What kind of problems do you solve?
What other languages have you used?
What is your favorite language, and why?
Is "progammer" or "developer" in your job title?
Do you think Red should be for "everyone" (e.g., like Visual Basic)?
Do you want to use Red for real work, or just fun?
What software do you pay for?
Keep the Red light burning!
@dockimbel I see, thanks for explanation! Interestingly, in older version it doesn't grow though:
>> probe now/time stats 6:04:59 == 3399680 >> probe now/time stats 6:05:00 == 3399680 >> probe now/time stats 6:05:01 == 3399680 >> probe now/time stats 6:05:02 == 3399680 >> probe now/time stats 6:05:03 == 3399680 >> probe now/time stats 6:05:04 == 3399680 >> probe now/time stats 6:05:04 == 3399680 >> probe now/time stats 6:05:05 == 3399680 >> probe now/time stats 6:05:06 == 3399680 >> system/build == make object! [ date: 15-Aug-2018/16:18:40+03:00
github-v3.redanymore. It's fixed now, so you can do
github/make-gist %script.red "Gist description"again, if you're into that kind of thing. There may be other broken functions, but I can't find their changelog, if they have one and don't have time to check rest of it now, so either be patient or report problems, if you encounter any.
Is this expected ?
>>>myobj: make object! [afunction: does [afunction2: [one oooo two ttt]]] >> myobj/afunction == [one oooo two ttt] >> myobj/afunction/(afunction2) == [one oooo two ttt]
>>>myobj: make object! [afunction: does [afunction2: [one oooo two ttt]]] >> myobj/afunction == [one oooo two ttt] >> myobj/afunction/(afunction2) *** Script Error: afunction has no refinement called (afunction2) *** Where: afunction *** Stack: >>
@9214 I am experimenting with paths, as you have read in my recent messages.
I was trying to understand is using (parens) notation around a word in a path could exectute a function and have the result as basis for the next step of the path.
myobj: make object! [afunction: does [afunction2: [one oooo two ttt]]]
I am interested interested into expressing like
"afunction2" should be exectued
@9214 Paths actually pick and select but if they pick a function inside an object and I ask for the result to be evaluated using a dedicated syntax, then the next step of the path should receive the result of the evaluation.
Let's suppose double ^ execute functions if found:
myobj: make object! [afunction: does [append: [one oooo ] [two ttt]]] myobj/^afunction^/two
Think about "afunction" selects from an external SQL source, then the result shouls be availabe to the path for being picked.
More one this:
myobj: make object! [afunction: funct [a b] [append: [one oooo ] reduce [A B]]] myobj/^afunction two ttt^/two