How to convert a string to visa resource name

[RTSLVU]

---

@crossrulz wrote:

---

@RTSLVU wrote:

---

@billko wrote:

---

---

Only if you have an aversion to coercion.  😉

---

IMHO: Coercion dots are a sign of failure 😛

---

That's a little extreme.  Coercion Dots are red flags to issues, not a sign of complete failure.

---

No it means *I* have failed, regardless of if the program works.

I have to add way back when we were moving from LV5.1 to LV 6i there was a lot of things the would no longer work after importing them into LV 6i because coercion of this or that was no longer supported.

A lot of code had to be rewritten and I don't want to ever go through that again.

[mcduff]

In newer LabVIEW versions you can use the "Coerce to Type"

It coerces without a dot. 🙂

mcduff

[billko]

---

@mcduff wrote:

In newer LabVIEW versions you can use the "Coerce to Type"

It coerces without a dot. 🙂

mcduff

---

Is that the application of a "gentle" coercion?  😄

[paul_cardinale]

---

@RTSLVU wrote:

---

@crossrulz wrote:

---

@RTSLVU wrote:

---

@billko wrote:

---

---

Only if you have an aversion to coercion.  😉

---

IMHO: Coercion dots are a sign of failure 😛

---

That's a little extreme.  Coercion Dots are red flags to issues, not a sign of complete failure.

---

No it means *I* have failed, regardless of if the program works.

I have to add way back when we were moving from LV5.1 to LV 6i there was a lot of things the would no longer work after importing them into LV 6i because coercion of this or that was no longer supported.

A lot of code had to be rewritten and I don't want to ever go through that again.

---

Sure, LV 5 -> LV 6 was painful; and so was LV 7 -> LV 8.  But since then upgrades have been smooth.  Personally, I would rather have coercion dots than extra code that does exactly the same thing.

[RTSLVU]

---

@paul_cardinale wrote:

---

@RTSLVU wrote: No it means *I* have failed, regardless of if the program works.

I have to add way back when we were moving from LV5.1 to LV 6i there was a lot of things the would no longer work after importing them into LV 6i because coercion of this or that was no longer supported.

A lot of code had to be rewritten and I don't want to ever go through that again.

---

Sure, LV 5 -> LV 6 was painful; and so was LV 7 -> LV 8.  But since then upgrades have been smooth.  Personally, I would rather have coercion dots than extra code that does exactly the same thing.

---

As long as coercion always works the way you want it to, I guess that's okay...

But I don't want to rely on something that is out of my control to always be the same when it's simple to do it the right way from the start.

[Yamaeda]

---

@RTSLVU wrote:

---

As long as coercion always works the way you want it to, I guess that's okay...

But I don't want to rely on something that is out of my control to always be the same when it's simple to do it the right way from the start.

---

There's some instances where the implicit coercion is faster than an explicit one. I guess it has something to do with memory copies, otherwise it makes no sense. 

/Y

[crossrulz]

---

@Yamaeda wrote:

There's some instances where the implicit coercion is faster than an explicit one. I guess it has something to do with memory copies, otherwise it makes no sense. 

---

The only place I know for sure is when debugging is on (additional hooks needed for the extra wire to be probed, etc).