Skip to content
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

Badval constructor #188

Merged
merged 4 commits into from Jun 14, 2016
Merged

Badval constructor #188

merged 4 commits into from Jun 14, 2016

Conversation

drzowie
Copy link
Contributor

@drzowie drzowie commented Jun 13, 2016

Propagate BAD values in constructor calls of the form '$a=pdl( pdl("BAD,5"),7);'

@coveralls
Copy link

Coverage Status

Coverage remained the same at 62.696% when pulling 17332b6 on badval-constructor into ca9af27 on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 62.696% when pulling d12d7b1 on badval-constructor into ca9af27 on master.

@wchristian wchristian merged commit d12d7b1 into master Jun 14, 2016
@wchristian wchristian deleted the badval-constructor branch June 14, 2016 02:30
zmughal added a commit that referenced this pull request Jul 10, 2016
The changes in <#188> broke the
build for all cases of `BADVAL_USENAN` xor `BADVAL_PER_PDL`.

This was because the checking for badvalues when copying in
`pdl_kludge_copy_*` did not take into account these variations in
accessing and setting the badvalue.
zmughal added a commit that referenced this pull request Jul 11, 2016
The changes in <#188> broke the
build for all cases of `BADVAL_USENAN` xor `BADVAL_PER_PDL`.

This was because the checking for badvalues when copying in
`pdl_kludge_copy_*` did not take into account these variations in
accessing and setting the badvalue.

For example, a simple comparison using `==` is not valid when of NaN
values are being compared. Here we need to use `!finite(...)` to make
the comparison if the type can use NaN values.
zmughal added a commit that referenced this pull request Jul 11, 2016
The changes in <#188> broke the
build for all cases of `BADVAL_USENAN` xor `BADVAL_PER_PDL`.

This was because the checking for badvalues when copying in
`pdl_kludge_copy_*` did not take into account these variations in
accessing and setting the badvalue.

For example, a simple comparison using `==` is not valid when NaN
values are being compared. Here we need to use `!finite(...)` to make
the comparison if the type can use NaN values.
wchristian pushed a commit that referenced this pull request Aug 22, 2016
The changes in <#188> broke the
build for all cases of `BADVAL_USENAN` xor `BADVAL_PER_PDL`.

This was because the checking for badvalues when copying in
`pdl_kludge_copy_*` did not take into account these variations in
accessing and setting the badvalue.

For example, a simple comparison using `==` is not valid when NaN
values are being compared. Here we need to use `!finite(...)` to make
the comparison if the type can use NaN values.
wchristian pushed a commit that referenced this pull request Aug 29, 2016
The changes in <#188> broke the
build for all cases of `BADVAL_USENAN` xor `BADVAL_PER_PDL`.

This was because the checking for badvalues when copying in
`pdl_kludge_copy_*` did not take into account these variations in
accessing and setting the badvalue.

For example, a simple comparison using `==` is not valid when NaN
values are being compared. Here we need to use `!finite(...)` to make
the comparison if the type can use NaN values.
d-lamb pushed a commit that referenced this pull request Jan 19, 2019
The changes in <#188> broke the
build for all cases of `BADVAL_USENAN` xor `BADVAL_PER_PDL`.

This was because the checking for badvalues when copying in
`pdl_kludge_copy_*` did not take into account these variations in
accessing and setting the badvalue.

For example, a simple comparison using `==` is not valid when NaN
values are being compared. Here we need to use `!finite(...)` to make
the comparison if the type can use NaN values.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants