Recent Posts

Pages: 1 [2] 3 4 ... 10
11
SlickEdit® / Re: small bug with column indicator in utf-8 coded files
« Last post by vladie on February 25, 2021, 09:24:54 am »
By “chars” do you mean UTF-32? That would count each Utf-8 character specification which is anywhere from 1-6 bytes as one character.

my source code is in utf-8, os is mac os.
12
SlickEdit® / Re: Parsing problem with concatenated strings
« Last post by rjpontefract on February 24, 2021, 10:29:44 pm »
Hi Dennis
The language mode is C/C++.
13
SlickEdit® / Re: Parsing problem with concatenated strings
« Last post by Dennis on February 24, 2021, 10:27:01 pm »
I will look into it.  Is the language mode C/C++ or ANSI-C ?  I think it is probably trying to resolved a user-defined string name.
14
SlickEdit® / Re: small bug with column indicator in utf-8 coded files
« Last post by Clark on February 24, 2021, 09:38:32 pm »
If you want a character count and not a byte count of a string of characters within a single line, make a selection and SlickEdit will give you a UTF-32 (not UTF-16) character count. In your case, since your sample text has no spaces, just double click on the word and SlickEdit will give you the character count (Utf-32 count not Utf-16) and not the byte count in the status area.

There's no need to do math on the start and end columns.
15
SlickEdit® / Parsing problem with concatenated strings
« Last post by rjpontefract on February 24, 2021, 08:29:27 pm »
Using SE 25.0.1, the following macro usage for FORMAT_STRING is highlighted as "symbol not found".  If I insert spaces around the macro usage it works as expected.  Unfortunately this is code that I can't change.  Is it possible to improve SEs parsing in this case?

Code: [Select]
#define FORMAT_STRING "%d"

int main(int argc, char**argv)
{
  int x = 42;
  printf("This is an example "FORMAT_STRING" with a format string", x);
}
16
SlickEdit® / Re: small bug with column indicator in utf-8 coded files
« Last post by Clark on February 24, 2021, 06:04:57 pm »
By “chars” do you mean UTF-32? That would count each Utf-8 character specification which is anywhere from 1-6 bytes as one character.

Your source code example doesn’t indicate the need for a particular length since the string is null terminated. To determine the amount of memory required by your sample string, you would need a byte count and not a UTF-32 count.

Note that on windows, SlickEdit uses the active code page by default for C++. I’m assuming you are on macOS or Linux.
17
SlickEdit® / Re: small bug with column indicator in utf-8 coded files
« Last post by vladie on February 24, 2021, 05:17:34 pm »
I've tried to measure utf-8 line width in chars using column values at begin and end of string, like:
const char *test = "приветприветприветприветприветприветприветприветприветпривет";

i think that it will be fine to have right-click popup menu on "Col" indicator, which can make possible to select Column meaning: it's offset in characters or in bytes.
18
SlickEdit® / Re: SlickEdit Pro 2020 crash
« Last post by patrick on February 24, 2021, 04:29:11 pm »
Fixed the problem for the next release, but it is not hot-fixable.  Post what platform you're on and whether it's 64 or 32 bit, we'll provide you with an updated exe/DLL.
19
SlickEdit® / Re: small bug with column indicator in utf-8 coded files
« Last post by Clark on February 24, 2021, 03:26:52 pm »
Right now, the column indicator is in bytes (Utf-8 for Unicode files) with tabs expanded. What the column indicator should be is not obvious. Some compilers still output error message column output exactly like SlickEdit does (especially Unix tools and SlickEdit tools). However, Microsoft tools seem to output Utf16 columns (NOT Utf-32). I don't see Utf-16 as an improvement. I like Utf-32 but there are no tools that use this (at least I haven't seen any).

So here's my question. What are you using the column indicator for? Are you trying to get a character count? If so, why do you need this count (i.e source code string length or matching another tools column??)? Do you want Utf-16, Utf-32, or Utf-8.  See what I mean???
20
SlickEdit® / Re: SlickEdit Pro 2020 crash
« Last post by patrick on February 24, 2021, 03:13:04 pm »
Reproduced here, taking a look at it.
Pages: 1 [2] 3 4 ... 10