Recent Posts

Pages: [1] 2 3 ... 10
1
Features and/or Improvements / Support for Java 9
« Last post by fhlbrep on November 22, 2017, 08:24:50 pm »
This is probably in the works, but I have not seen any mention of it. Looking to upgrade an older version of SE to a newer one which will support Java 9 SDK and modules.
2
SlickEdit® / Re: Several problems with Golang support
« Last post by Dennis on November 22, 2017, 08:19:41 pm »
Issue #2 will be fixed in 22.0.1.
3
This will be fixed for v22.0.1
4
SlickEdit® / Re: Several problems with Golang support
« Last post by asandler on November 22, 2017, 06:58:35 pm »
Thanks.
5
SlickEdit® / Re: Several problems with Golang support
« Last post by Dennis on November 22, 2017, 06:48:12 pm »
Finally got back to this one, that is:  Issue #2.

I'll take a look at this and see if I an improve the Go local variable parsing to deal with the lack of statement terminators.  Your example works fine if you put semicolons at the end of each line (like most well conceived languages require)
6
SlickEdit® / Re: v22 memory leak?
« Last post by JeffB on November 22, 2017, 05:54:57 pm »
FYI...After sitting for a few days with only minor usage, the resident memory is 6.35GB and Virtual is 7.5GB.
7
SlickEdit® / Suggestion: Vim command mode should be normal mode
« Last post by davea on November 22, 2017, 04:52:35 pm »
Now that vi emulation has actually been Vim emulation for quite some time now, I think the '-- COMMAND --' mode text should be changed to '-- NORMAL --' in order to properly mirror long-standing Vim behavior...and possibly to encourage proper Vim usage patterns. ;D

See: http://vimdoc.sourceforge.net/htmldoc/intro.html#vim-modes-intro

I had experimented with trying to change this myself within the Slick-C code some time ago, but it appears that there may be an instance of this text somewhere within the SlickEdit base code since the old text continued to appear in certain instances.

Thanks,
Dave
8
SlickEdit® / Re: Edge case c++ auto keyword and list-symbols
« Last post by mrothman on November 22, 2017, 03:20:58 pm »
And one more piece of info: if I change the -> to a ".", the correct attributes for an std::shared_ptr are listed, so it does know that my variable is a shared_ptr, it just doesn't seem to be able to deal with the -> operator on it.  For fun I tried:
auto foo = std::make_shared<std::vector<myType>>();
foo.get()-> // now try to list symbols with caret right after the ->

but it didn't go for that either (same error message).
9
SlickEdit® / Re: Edge case c++ auto keyword and list-symbols
« Last post by mrothman on November 22, 2017, 02:41:56 pm »
More info: I changed the following:
1) Under C/C++ Compiler properties in the Options section, I created a gcc 6.3 Name and configuration and pointed it at the compiler include directories for 6.3.0.  Not quite sure what the "Header File" option is.  I deleted the rest of my Compiler Configurations since they were hopelessly old.  I deleted the tag file(s) for those older include directories also.
2) Under the "Build" menu, I specified the Compiler by putting in the entire path to the executable for gcc 6.3.0
3) In the Project Properties dialog, I specified under the "Compiler/Link" tab the gcc 6.3.0 configuration (which is now the only one I have).

I closed SlickEdit, saving config and then re-opened.  I still get the same error message when trying to list symbols for the variable whose type was specified as "auto".  Let me know if a) I need a later gcc and b) there are other places in the configuration I need to touch.  Thanks.
10
SlickEdit® / Re: Edge case c++ auto keyword and list-symbols
« Last post by mrothman on November 22, 2017, 01:23:51 pm »
Hi Dennis.  So interesting question.  We build with a makefile which among other things points onto our network at in whatever version of gcc our systems team has validated our code base against.  That happens to be 6.3.0 at the moment.  BUT I doubt that this would be visible at all to SlickEdit (since we build with our Makefile). So I suspect that what you are asking is what version is SlickEdit using to analyze the code?  I hadn't explicitly set that, since I didn't know it was even a factor.  It looks like it happens to be 4.72 (ouch, that wouldn't even have c++11 !).  I probably can download and put any version of gcc in place for SlickEdit that you would recommend, since it would have no effect on our build.  Meanwhile I'll try whatever latest version we have around here and see if that makes a difference.
Pages: [1] 2 3 ... 10