Hi folks,
I don't know if anyone here can help, but we are at wits' end. We use the Facets product from Trizetto, and I inherited an extension that works fine in production. All I changed was one URL in one method and its overload, and now none of us can run it in either Windows 7 or XP SP3. Debugging it or running the installed extension gives the error shown. The extensions guide (like much of what Trizetto has put out) is pretty useless, and they have no support links or knowledge base online. Has anyone encountered this sort of thing, and can you lead me to any possible solutions?
Trizetto is fairly straight forward for extensions. In this case your custom code is returning an error when Facets attempts to invoke it. Can you run your code outside of Facets and see what happens? A test rig helps here.
Related
I am kinda of a new user here and don't have enough reputation points to comment/ask on this question: IDE support for Hack Lang.
So, I am hoping that since the last entry provided by Themis Beris someone has been able to get PHPStorm working properly with Hack. I followed the 3 steps described in the post I mentioned, but still get compile-time errors on the classes I've written using Hack. <?hh is not recognized, for instance.
Any suggestions as to how to get PHPStorm playing nice with Hack?
I have no idea what Themis Beris is talking about on the linked question. (He seems to be saying something about PHPUnit, which is a completely separate issue.)
JetBrains has a feature request open for Hack support and last I heard was very actively working on it. But as of this writing (Feb 2015) it's not released yet.
I'm not completly sure if it's proper to ask this here, but...
I'm a student forced to work with Code:Blocks IDE on Win7 (64 bits), and it keeps crashing everytime I try and add/edit an #include, I've tried in both C and C++ and I think it's got to do with the editor since it compiles correctly.
Has anybody else had this problem? Is there any way to fix it?
Best bet would be to search through the Code::Blocks ticketing system to see if anyone knows about the problem.
If no-one does, then raise a ticket yourself.
It'd also be a good idea to provide as much information there up front as possible, such as the source files (or enough of them to cause the actual problem), project settings, IDE version, and so on.
That'll get your ticket moving along faster than if they have to chase you for the information.
I have downloaded multiple OCaml IDE's / plugins and NONE of them work. I have no clue if I have a directory problem or if something else is at fault. I can access the OCaml console through cygwin just fine but it is not very useful for dealing with larger files. I am a total OCaml noob and have no clue how to fix my problems. I have been reading every post on OCaml here and nothing is helping. I am hoping that somebody can help me because this is very frustrating! Thanks to all who reply.
OCaml modes for Emacs and Vim work perfectly (and they run on MacOS and Windows, of course). I heard Geany works well as well.
I'm not saying everyone must learn Emacs and Vim; I understand that it's a kind of interface that beginners maybe don't want to get into -- and supporting other editors well for OCaml is a problem that we need to fix. But if you want reasonable support for pretty much every kind of text format out there, they're still good choices.
Finally, if you have a decent terminal / command-line (if you are on Windows that might require running a GNU/Linux virtual machine), pretty much every editor will be fine if you compile stuff by hand from the terminal (which is not particularly hard). In-Editor support will still provide you with a better experience, in particular allowing to jump right to the place in your code where the compiler says there is an error, but as a beginner you can go a long way without even that.
PS: it would be extremely useful if you took the time to spell out precisely what your problem with each tool was, and send that information to the respective maintainers. I think the main problem with these tools is the lack of testers. Help the future people that will try these tools by helping the maintainers fix them!
I'v recently looked at OcaIDE for eclipse - and it seems to work.
You need perhaps set some configuration variables (paths to ocaml compiler,...), but I don't remember any quirks.
I would like to thank everybody for their help. I finally found some installation instructions for the tuareg mode in EMACS. In case anybody else is having the same problem that I was there are VERY clear instructions here
How to install tuareg
Hopefully I can now translate some stuff into OCaml that I have been working on in other languages and post some of my projects. Thanks again for all of the help.
You can use Notepad++ for Windows. It is more intuitive for than Vim or Emacs for the beginners. And it has a syntax highlighting for Caml and you can assign hotkeys for compiling executing the program.
I would suggest using OcaIDE. I've done some fairly large projects with it, and it's not bad. Emacs (with Tuareg mode) is also a good option. If you're having trouble with setup, I wrote a guide for OS X: http://www.princeton.edu/~crmarsh/ocaml_dev_environment/
I'm currently trying to compile an old program (made with C++ builder 2 or 3) with the "current" Embarcadero RAD Studio XE2.
So, I was wondering whether there is an easy way to use the old code, as Borland once claimed to be fully compatible to lower versions... however I couldn't find a "project-file", only source-code (.cpp, .h, .res, etc.).
I tried to "add to project" the main .cpp, however there seem to be some wrong include-paths... it also seem to use the OWL-package and includes its important source-files...
I'm a bit confused which type of main project I have to open first, since you need to open a new project before adding the source to it. As the running .exe has a GUI, I tried a Form-Window first, but it may be better to use a console or service as the real form is produced within the code as far as I understand.
So, after installing OWL and correcting the include-paths, do you think it should be running fine? Or is there something else to take care of?
If your old project was using OWL, you're probably well outside of the supported upgrade path.
That being said, valid C++ code should still compile and work and I've heard of people using OWL with recent versions of C++Builder. (via OWLNext)
Regarding your confusion as to which type of project to use, I believe a console application would be your best bet. A forms application is completely wrong, that will bring in the VCL and give you no end of problems trying to reconcile the different windowing systems. A service application is a completely different beast as well, and isn't meant for GUI applications. A console application should work, but you'll need more. The OWLNext project has a wiki that should help quite a bit.
I just downloaded the trial for this application and it doesn't seem to work. I went through the Quick Setup guide and it all looked great. Now when I place my cursor on a member of any type and press Ctrl+Shift+D it does nothing. I placed it on top, inside, etc... Nothing. If I press Ctrl+Shift+A (twice) on top of the member it tells me to place it "in the line of the form MyType myVariable;". I'm not quite sure what this means unless it's referring to C# but this project is VB.NET which it doesn't seem to recognize. Anyone else have this issue? I was hoping it would make things easier since I've read that it can document an entire document rather than having to member by member.
Using VS 2010 Premium.
Drop me an email to support (at) atomineerutils.com with a bit of example code that exhibits the problem, and I'll help you sort it out.
(edit)
Please note that AtomineerUtils only officially supports VB 9 onwards, although where the syntax of earlier versions is compatible (i.e. in most cases), it will still work perfectly well.
I've now investigated this, and I can't repeat the documentation behaviour you have mentioned - it works as expected for me. (However, I did find and fix a regression introduced to the Visual Basic handling in a recent version - a small coding glitch that meant some methods could be incorrectly documented as constructors, so thanks for indirectly helping me find this issue!)
All I can suggest is that if you see a problem in any application, the best (and often only) way to get it fixed is to let the author know!