This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hello, I created a new user type that is a byte array property on the class, but a string in the database. A convertor class is then responsible for reading and writing the byte array while the string in the database contains the filename where the data was written. However, when one specified "byte[]" as the CLR type, LightSpeed generates "@byte[]" resulting in a compiler error. The only way I found to fix it was to use "Byte[]". Since there is a workaround, its not critical, but I thought you may be interested. Thanks, Werner |
|
|
|
|
Thanks for letting us know about this. As you've found, we do currently require that users enter the CLR type name rather than the C# or VB type name (though it's unavoidable to use language-specific warts when specifying an array), but I'll log a feature request to detect when users enter language keywords and suppress the @ escaping. (Unfortunately, we would have to implement a special case for this, because the @ escaping isn't done by us -- we just ask the C# engine in the .NET framework to format the CLR type name, and it goes "gosh, that clashes with a keyword, I'd better escape it" rather than "that's a built-in type name, leave it alone.") |
|
|
|
