InterviewSolution
Saved Bookmarks
InterviewSolution
| 1. |
Solve : Perfered Programming Language? |
|
Answer» Another bump?batch is good, but its even better when you add VBScriptWho said this: Who said this: I think I did. Quote they don't want to rewrite in C++ are any other languagec++ or java or computer apps for school. What do you guys thinkQuote QuoteWhat I meant was that a project may have built several apps in C ++ and each APP has its own main thing and the apps are not integrated together. So the project leader says the apps have to be integrated. Oops. They have conflictual thing sin them and they do not really work together. What the boss wants is a package that makes it loot like one big application. So the programmers do not want to re-write the apps so that can all be in one big EXE. So they use a script language like TCL to do a GUI that gives a look and feel of a kind of integrated app. The TCL is just a user interface that lets the user pick an app from a list. Do you understand what I mean? The advantage of TCL is it can do a simple GUI that looks nice in windows. I may have exposed a inside secret. Sorry. I can't keep my beak shut.OK -- cool -- I'll have to keep that in mind.Snit looks fun... Quote from: Wikipedia Snit is intended to HELP build applications out of the code at hand.I've voted C++. I think that C is the de-facto standard in UNIX but the ORIGINAL C language lacked many features (reference, template, STL, string, overloading, class, etc.). I currently use lots of these features in C++ now.C, not C++, is the de-facto standard of UNIX and is what UNIX is written in, as well as most of it's user-based derivatives, such as Ubuntu, GNU,Fedora, and so forth. in my opinion C++ is a somewhat rushed implementation of OOP into the existing C language. The fact that one needs to define the class interface and the concrete class itself in separate HEADER and cpp files makes file management a unnecessary pain in the but. Additionally, although simply using classes in C++ is workable, a completely different set of difficulties arises when trying to implement COM classes via C++. with requirements to implement IUnknown, IDispatch, IPersistFile, IObjectSafety, and goodness knows how many other COM interfaces, many of which contain basic boilerplate code (which can be easily wrapped into templates as shown by ATL). of course this isn't really a design flaw on the part of C++ but rather the lack of anything higher-level to the C++ programmer for COM components. As an example, Visual Basic and Delphi can both implement COM classes without requiring the programmer to manually implement the various required classes (IClassFactory and so forth) |
|