-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[devs] allows negative time in time advance #241
Comments
quesnel
pushed a commit
to quesnel/vle
that referenced
this issue
Aug 26, 2016
If a vle::devs::Dynamics::timeAdvance returns a negative value, VLE kernel will interpret this value as an absolute date instead of a duration. Seems to be useful to (re)synchronize model with integer dates and permits to reduce real representation problems. (closes: vle-forge#241).
However: how to build negative absolute date? Prohibits negative begin date? |
quesnel
pushed a commit
to quesnel/vle
that referenced
this issue
Sep 12, 2016
If a vle::devs::Dynamics::timeAdvance returns a negative value, VLE kernel will interpret this value as an absolute date instead of a duration. Seems to be useful to (re)synchronize model with integer dates and permits to reduce real representation problems. (closes: vle-forge#241).
quesnel
pushed a commit
to quesnel/vle
that referenced
this issue
Sep 22, 2016
If a vle::devs::Dynamics::timeAdvance returns a negative value, VLE kernel will interpret this value as an absolute date instead of a duration. Seems to be useful to (re)synchronize model with integer dates and permits to reduce real representation problems. (closes: vle-forge#241).
quesnel
pushed a commit
to quesnel/vle
that referenced
this issue
Oct 24, 2016
If a vle::devs::Dynamics::timeAdvance returns a negative value, VLE kernel will interpret this value as an absolute date instead of a duration. Seems to be useful to (re)synchronize model with integer dates and permits to reduce real representation problems. (closes: vle-forge#241).
quesnel
pushed a commit
to quesnel/vle
that referenced
this issue
Nov 9, 2016
If a vle::devs::Dynamics::timeAdvance returns a negative value, VLE kernel will interpret this value as an absolute date instead of a duration. Seems to be useful to (re)synchronize model with integer dates and permits to reduce real representation problems. (closes: vle-forge#241).
quesnel
pushed a commit
to quesnel/vle
that referenced
this issue
Dec 12, 2016
If a vle::devs::Dynamics::timeAdvance returns a negative value, VLE kernel will interpret this value as an absolute date instead of a duration. Seems to be useful to (re)synchronize model with integer dates and permits to reduce real representation problems. (closes: vle-forge#241).
@duboz : we merge this behaviour in VLE2 or not? |
quesnel
pushed a commit
to quesnel/vle
that referenced
this issue
Mar 29, 2017
If a vle::devs::Dynamics::timeAdvance returns a negative value, VLE kernel will interpret this value as an absolute date instead of a duration. Seems to be useful to (re)synchronize model with integer dates and permits to reduce real representation problems. (closes: vle-forge#241).
quesnel
pushed a commit
to quesnel/vle
that referenced
this issue
Nov 10, 2017
If a vle::devs::Dynamics::timeAdvance returns a negative value, VLE kernel will interpret this value as an absolute date instead of a duration. Seems to be useful to (re)synchronize model with integer dates and permits to reduce real representation problems. (closes: vle-forge#241).
quesnel
pushed a commit
to quesnel/vle
that referenced
this issue
Jan 17, 2019
If a vle::devs::Dynamics::timeAdvance returns a negative value, VLE kernel will interpret this value as an absolute date instead of a duration. Seems to be useful to (re)synchronize model with integer dates and permits to reduce real representation problems. (closes: vle-forge#241).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A funny behaviour: if a
vle::devs::Dynamics::timeAdvance
returns a negative value, VLE kernel will interpret this value as an absolute date instead of a duration. Seems to be useful to (re)synchronize model with integer dates and permits to reduce real representation problems.The text was updated successfully, but these errors were encountered: