Any reason why this is not just a bug: <https://tr...
# lucee
a
Any reason why this is not just a bug: https://trycf.com/gist/4ea12a5aeb28148571a962e361228834/lucee5?theme=monokai
Copy code
try {
    throw(message="SAME_MESSAGE_AND_DETAIL", detail="SAME_MESSAGE_AND_DETAIL")
} catch (any e) {
    writeDump([
        message = e.message,
        detail = e.detail // where gone?
    ])
}

try {
    throw(message="DIFFERENT_MESSAGE", detail="DIFFERENT_DETAIL")
} catch (any e) {
    writeDump([
        message = e.message,
        detail = e.detail
    ])
}

https://i2.paste.pics/35fd501360fba93bed8162716fd57211.png

👀 2
🤔 1
And, yes, I know it would be unusual to have the same message and detail, but that's beside the point. It's not for Lucee to be going "ooh no, we can't have that: I'll blank that detail out. There. That's better." Also: note that CF just does what it's told.
d
If it walks like a duck, quacks like a duck, well it's probably a duck. 😄 (Yes, it looks like a bug to me.)
1
a
My only apprehension is that one would need to specifically write code to have it work the way it does, so I'm guessing there was some reasoning behind it.