Is it possible to compile (to a COM file) from the command-line using Turbo Pascal 3.0? No matter what arguments I try with TURBO it launches the IDE.
Your best bet is to upgrade to Turbo Pascal 5, which has TPC.EXE, the commandline tool. Turbo Pascal 3.02 only has TURBO.COM.
Related
How do I compile coffee script in Notepad++ to check that it works before reloading the web page? Are there any plugins available, particularly for the node.js coffeescript compiler?
I have written as simple bat file at [https://github.com/obromios/coffee_short_black][1], that uses the Notepad++ run capability and can use the node.js compiler. It provides an easy way to view error messages and to view the compiled script. It is not a plugin, but is as easy to use as a plugin.
I am new to selenium 2.0 and working on automation through perl and java(maven-eclipse). I want to know the perl bindings for Se differ.
Selenium website shows https://metacpan.org/module/Selenium::Remote::Driver
While CPAN also has WWW:Selenium bundle....
Which to use to perl automation in this context?
Selenium::Remote::Driver is the one you want. WWW:Selenium is old.
You can visit the following URL:
http://repo1.maven.org/maven2/org/seleniumhq/selenium/client-drivers/selenium-perl-client-driver/
I am writing a scala editor and would like to leverage ctags for method and variable lookups. A quick search on internet indicates that this may have been done before, but can not locate how.
Ideally, i would like to leverage it in conjunction with something like Exuberant Ctags but it would be great if there was something that was platform independent (Exuberant Ctags seems to be based on C ).
any help on this would be appreciated.
or should I just use apache lucene ?
There's no such thing as "platform independent". Java requires the java executable, which is written in C. Same thing for Python, Ruby, Perl, etc. So, as long as there is an exuberant-ctags available, why bother with anything else?
EDIT
The link I originally had here, about Scala ctags and vim tagbar, is no longer valid. I thought of replacing it with something else, but googling for "scala ctags" or "scala tagbar" yield lots of stuff, and will remain up-to-date.
Exuberant Ctags supports far more than just C:
$ ctags --list-languages
Ant
Asm
Asp
Awk
Basic
BETA
C
C++
C#
Cobol
DosBatch
Eiffel
Erlang
Flex
Fortran
HTML
Java
JavaScript
Lisp
Lua
Make
MatLab
ObjectiveC
OCaml
Pascal
Perl
PHP
Python
REXX
Ruby
Scheme
Sh
SLang
SML
SQL
Tcl
Tex
Vera
Verilog
VHDL
Vim
YACC
$
Perhaps extending the Java language recognizer for Scala would be a good start?
Exuberant Ctags runs on Windows 98/NT/2000/XP, VMS, and (almost every?) Unix and Unix clone. I couldn't find a list of platforms where Exuberant Ctags doesn't run, anyway...
I want to create 64 bit apps for (for example) 64 bit Windows 7. I've searched the web and found some help but couldn't get it to work.
Sorry I've taken so long to respond but I have tried to get the packages suggested to work but they're not easy or else I'm doing something wrong.
Anyway I ran across an environment called pellesc. It consists of a development environment around a compiler which traces is roots back to a 32-bit version that was once (according to Wikipedia) used to develop Quake. From what I've seen so far it's very promising and generates good code too!
In spite of what other people are saying, Eclipse actually has very good support for C++, even in Windows: check out the CDT project. It's very mature and well-supported -- it works for C/C++ at least as well as Eclipse JDT works for Java.
As for the compiler itself, VonC is right, MinGW-w64 (but the mingw-w64 project is moving to mingw-w64.org so i suggest to use mingw-w64.org) is the best option. Eclipse CDT has built-in support for MinGW so as long as you install MinGW first, Eclipse should automatically detect it.
This Eclipse MinGW64 tutorial mentions:
update (Nov 9, 2010): recent MinGW-w64 versions come with 'as', 'g++', and 'gcc' commands. This step may be unnecessary in your MinGW build.
Meaning you won't have anymore to update the GCC assembler, C++ compiler, C compiler and C++ linker, with 'x86_64-w64-mingw32-as', 'x86_64-w64-mingw32-g++', 'x86_64-w64-mingw32-gcc', and 'x86_64-w64-mingw32-g++'.
Other great source for w64 development tools:
Native windows x64 software develop with Mingw-w64 on drangon.org
A 64-bit version of GCC for Windows is available at http://tdm-gcc.tdragon.net/download. I can't see why you would want to use Eclipse for C or C++ programming - try the Code::Blocks IDE at http://www.codeblocks.org instead.
Honestly, I use cygwin. Its compatable with unix so you can easily move systems and has tons of functionality that is gcc friendly (autoconf, make, makedepends, ...). To use gcc to compile to 64 bit add the -m64 option. To compile for windows use the -mno-cygwin option. Make sure though that you're using gcc 3 and not 4 (then you'd use the mingw compiler series). Otherwise, its all the same as unix which is really useful.
I am looking at embedding perl 5.10 in a large C++ application compiled with VC++ 6.0. This leads to two questions.
1) Is it a bad idea to simply use Strawberry Perl as a dependency rather than compile my own perl with VC++ 6.0? Would Strawberry even work given the compiler mismatch? I presume Strawberry is compiled with mingw. I would much rather not have to keep my own custom perl build around.
2) If I went the Strawberry route, would something like Inline::C work in the embedded application? You'd have VC++ 6.0 code calling mingw compiled Strawberry in turn calling user mingw compiled code. Inline::C would be an awesome capability for what I'm trying to achieve with the embedded perl interpreter.
Given the uncertainty involved, I would recommend compiling Perl using MSVC instead of experimenting with Strawberry Perl for this application. There are instructions in perlwin32 and a related discussion on Perl Monks to guide you.
As a former release manager for Strawberry Perl, I can tell you it's not terribly difficult to do if you're comfortable with a compiler already.
-- xdg
Activestate perl is compiled with VC++ 6.0. It can use VC++ 6.0 or MinGW to compile modules since they link to the same C runtime library, msvcrt.dll. It would be preferable to use MinGW because VC++ 6.0 is neither free nor readily available (unless you can be sure that it is installed on the target machine.) You can PPM install Mingw now, and compile modules from CPAN. A large number of modules compile without trouble. You may have to configure CPAN with:
o conf yaml_module '' (Two single quotes, nothing between)
o conf commit
Inline::C works.