From b704ac0edaed6b2e77f74a484434f45d4c5b701d Mon Sep 17 00:00:00 2001 From: Brian Frank Date: Tue, 23 Apr 2024 10:41:59 -0400 Subject: [PATCH] Build 1.0.80 --- etc/build/config.props | 5 +++-- src/doc/docIntro/doc/ChangeLog.fandoc | 2 +- src/doc/docLang/doc/Actors.fandoc | 5 +++-- 3 files changed, 7 insertions(+), 5 deletions(-) diff --git a/etc/build/config.props b/etc/build/config.props index c1b535bfa..c90c4a2b1 100644 --- a/etc/build/config.props +++ b/etc/build/config.props @@ -11,7 +11,7 @@ // // default version used by build scripts -buildVersion=1.0.79 +buildVersion=1.0.80 // Must be configured boot build in substitute/release installation //devHome=/work/fan/ @@ -24,4 +24,5 @@ buildVersion=1.0.79 // dotnetHome=/C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/ // Mac setup -//jdkHome=/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/ \ No newline at end of file +//jdkHome=/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/ + diff --git a/src/doc/docIntro/doc/ChangeLog.fandoc b/src/doc/docIntro/doc/ChangeLog.fandoc index 57512c9a6..e337be11a 100644 --- a/src/doc/docIntro/doc/ChangeLog.fandoc +++ b/src/doc/docIntro/doc/ChangeLog.fandoc @@ -6,7 +6,7 @@ ** license: Licensed under the Academic Free License version 3.0 ************************************************************************** -*Build 1.0.80 (working)* +*Build 1.0.80 (23 Apr 2024)* - New ECMA class-based JavaScript design - Move fwt pods into separate repo - Crypto JWT and JWK APIs diff --git a/src/doc/docLang/doc/Actors.fandoc b/src/doc/docLang/doc/Actors.fandoc index f4dbeb3b4..41020fb96 100644 --- a/src/doc/docLang/doc/Actors.fandoc +++ b/src/doc/docLang/doc/Actors.fandoc @@ -96,7 +96,7 @@ Futures [#futures] ****************** All three send methods return a [Future]`concurrent::Future` which may used to access the result of that message. You can poll for the -result using `concurrent::Future.state` - a future enters the complete +result using `concurrent::Future.status` - a future enters the complete state by one of three transitions: - The actor processes the message and returns a result - The actor raises an exception while processing the message @@ -270,4 +270,5 @@ shutdown. Unlike 'stop', kill doesn't give actors a chance to finish processing their pending message queues - all pending messages are cancelled. Actors which are currently executing a message are interrupted (which may or may not immediately terminate that thread). Once all actors have -relinquished their threads, the ActorPool enters the *done* state. \ No newline at end of file +relinquished their threads, the ActorPool enters the *done* state. +