RE: [sv-ec] Eratta: String Methods Should be Functions not Tasks?

 
Chris,

Yes, I forgot that the conversion *to* string is not the exact reverse
of the conversion *from* a string. It should read:

3.7.11 itoa()
function void itoa(integer i);

3.7.12 hextoa()
function void hextoa(integer i);

3.7.13 octtoa()
function void octtoa(integer i);


-Dave

-----Original Message-----
From: owner-sv-ec@eda.org [mailto:owner-sv-ec@eda.org] On Behalf Of
Chris Pruett
Sent: Wednesday, September 28, 2005 7:49 AM
To: sv-ec@eda.org
Subject: [sv-ec] Eratta: String Methods Should be Functions not Tasks?


The LRM 3.1a appears to define all methods of the data type "string" as
tasks.  For example:

3.7.11 itoa()
task itoa(integer i)

3.7.12 hextoa()
task hextoa(integer i)

3.7.13 octtoa()
task octtoa(integer i)

As tasks they cannot be called by other functions.  Such data
manipulation methods should never block so shouldn't they be void
functions instead?