ENUM defaults

[Earn]

Shouldn't the default value of the first enumerator be 0 rather than 1?

Code Select Expand

ENUM test
t0
t1
t2
t3
t4
ENDENUM

OPENCONSOLE

PRINT t0, t1, ,t2, t3, t4

PRINT "Press Any Key"
DO:UNTIL INKEY$<>""
CLOSECONSOLE
END
Earn

[Rock Ridge Farm (Larry)]

I believe that most basic type languages start with 1.
I think starting with 0 is a 'C' concept.
Could be wrong - would not be the first time.

[ts-soft]

Use it in this way:

Code Select Expand

ENUM test
t0 = 0
t1
t2
t3
t4
ENDENUM

OPENCONSOLE

PRINT t0, t1, ,t2, t3, t4

PRINT "Press Any Key"
DO:UNTIL INKEY$<>""
CLOSECONSOLE
END
IMHO normal was beginning with 0

greetings
Thomas

[Earn]

Apparently Microsoft defaults it to 0 as it was an MS header I was converting when I came across the problem.  Couldn't find ENUM documented in the EB manual so I assumed ( ohh! That got me again) that the default index would be the same.
Earn

[LarryMc]

  Couldn't find ENUM documented in the EB manual...

You're correct but there is an example called enum.eba that may or may not have helped you.

This from the version announcement is a dead giveaway.:

Code:
ENUM days
monday
tuesday
wednesday
thursday
friday
saturday
sunday
ENDENUM

Would create a typedef named 'days' which is an INT and seven constants sequentially numbered from one.

Larry

[Ionic Wind Support Team]

It will be updated in the users guide when I get the chance.  Usually full updates are done with point releases, I just neglected to put the keywords in the alphabetical reference.

As for the default...it matches Aurora.  And I prefer it to start at 1 because I used it for control constants.

[Peter]

Wouldn't it be simple enough (although I don't know exactly how this is coded thus I might be wrong) to just add an option to enum?
The TYPE-statement has a perfect param, and this:

Code Select Expand

ENUM Days, 0

... would be an excellent way to choose which number to start from. If needed, even the STEP function could be useful.

Just a thought...

[LarryMc]

Code Select Expand

ENUM Days, 0

... would be an excellent way to choose which number to start from.

Again, from the example file, enum.eba:

Code Select Expand

ENUM days
Monday=3
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday
ENDENUM
print Monday
results in a 3
if you change it to Monday=0 then print Monday results in 0.

Larry

[Ionic Wind Support Team]

Larry, you are correct, there isn't a single "default" with enumerations.  You can use it the same way C does and specify multiple starting points, such as different messages and control identifiers:

ENUM ids
b_cancel
b_ok
m_open = 100
m_save
m_options
m_quit
m_cut = 200
m_copy
m_paste
m_search
ENDENUM

Paul.

[LarryMc]

didn't realize you could have that 2nd starting point in there.  That's neat!

So why would I want to use a bunch of const instead of using enum.

It appears this would solve what I have always seen as an aggravation of having a list of constants as control ID's or menu IDs and then needing to insert a new one and renumbering from there down.

Can I use the enum's exactly like const; in include files in multiple source files of a project?

What's the drawback, if any?

Larry

[Ionic Wind Support Team]

Yes, they are constants, and yes you can use them from an include.  They are just a compiler construct to make life easier.

You don't even need to use the automatic numbering and specify a value for each constant, which just saves having to type CONST or $define over and over.

Paul.

[LarryMc]

I like it; I like it!

Thanks

Larry