RE: only 16 enum states?

["Liyu, Andrei" <liyua@ornl.gov>]

About string.

I don't see problem.

Use waveform record with

...

field( FTVL, CHAR)

...

Moreover, EDM understands this.

 

What I like in Epics – that are CA and Libcom library. Both are based on reasonable ideas of control system.

 

Andrei.

 

 

 

-----Original Message-----
From: Dalesio, Leo [mailto:dalesio@slac.stanford.edu]
Sent: Tuesday, November 23, 2004 8:17 AM
To: Marty Kraimer; Dirk Zimoch
Cc: TECHTALK
Subject: RE: only 16 enum states?

 

This is one of several limitations that have existed from the start. We have a preliminary plan that we will present at the meeting at KEK. The short answer to handling this as well as the limited string length problem is that we plan to do it in version 4. This is 2 years away according to the plan. It requires at least a rewrite of the database access layer.

Bob

 

-----Original Message-----

From: Marty Kraimer [mailto:mrk@aps.anl.gov]

Sent: Tuesday, November 23, 2004 5:13 AM

To: Dirk Zimoch

Cc: TECHTALK

Subject: Re: only 16 enum states?

 

 

 

Dirk Zimoch wrote:

 

> Hi all,

>

> when I try to read the choices of an enum field, I only get the first

> 16. This ist not enough to read all the choices of the LINR field

> (menuConvert) if there are many breakpoint tables. It's even not

> enough to read all choices of the STAT field.

 

 

As you found out it is a problem in db_access.h, which describes that

data that passes through Channel Access.

 

>

> Is there a fix?

 

No.

 

>

> What happens if I change in db_access.h

>

> #define MAX_ENUM_STATES        16

>

> in

>

> #define MAX_ENUM_STATES        255

 

 

You will break any existing CA client and server that uses ENUMs

 

>

> ?

>

>

> Dirk

>

 

Perhaps Bob Dalesio can make a few comments about how we plan to address

this and other known problems created by db_access.h. For example

strings are limited to 40 characters. We hope to start addressing these

issues in the near future.