Re: Proposal for a (small) enhancement to the value() function.

new topic     » goto parent     » topic index » view thread      » older message » newer message

CChris wrote:
> 
> ChrisBurch2 wrote:
> > 
> > CChris wrote:
> > > 
> > > Currently, value(), defined in get.e, takes a sequence and returns {status
> > > code,
> > > value read}.
> > > The proposed enhancement is to return 
> > > {status code,
> > >  value read,
> > >  number of characters read,
> > >  number of leading whitespace characters}.
> > > 
> > > This can be done at the cost of creating a duplicated, slightly modified
> > > copy
> > > of the internal Get() function, so that performance won't be affacted at
> > > all.
> > > get() won't be affected, since where() will give you most of the same
> > > information.
> > > 
> > > Any thoughts? issues? other suggestions?
> > > CChris
> > 
> > If backwards compatability is not affected, then no problems - since I'm
> > only interested in value[2] its not a problem for me.
> > 
> > Chris
> 
> The only compatibility issue I can think of is that code that says:
> }}}
<eucode>if equal(value(s),{GET_SUCCESS,3.14}) then...</eucode>
{{{
 will break.
> Is it a problem?
> 
> CChris

It won't break any of _my_ code, so, for me, its not a problem. As to anyone
elses.......

Chris

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu