Skip to content

fix: use unsigned int so that 0xFFFFFFFF can be stored #32

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.

Sign up for GitHub

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

Open
aminya wants to merge 1 commit into
base: 7.x
Choose a base branch
from
Open

fix: use unsigned int so that 0xFFFFFFFF can be stored #32

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions opennurbs_defines.h
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2133,7 +2133,7 @@ class ON_CLASS ON
// the values. The reason for the gaps between the enum
// values is to leave room for future snaps with prededence
// falling between existing snaps
enum osnap_mode
enum osnap_mode: unsigned int
{
os_none = 0,
os_near = 2,
Expand Down Expand Up @@ -2409,7 +2409,7 @@ class ON_CLASS ON_COMPONENT_INDEX
// Do not change these values; they are stored in 3dm archives
// and provide a persistent way to indentify components of
// complex objects.
enum TYPE
enum TYPE: unsigned int
{
invalid_type = 0,

Expand Down
2 changes: 1 addition & 1 deletion opennurbs_object_history.cpp
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ class ON_Value
// The VALUE_TYPE enum values must never be changed
// because the values are used to determine the parameter
// type during file reading. Additions can be made.
enum VALUE_TYPE
enum VALUE_TYPE: unsigned int
{
no_value_type = 0,

Expand Down