Manufacturer: Computer Design Lab
Price: $89 US (per copy)
Reviewer: Eric Harlow
After having installed several compilers that consume 50 megabytes of disk space, it was a relief to install a compiler that was this small—less than one megabyte. The package includes some small sample programs and a small, yet fairly complete, manual that references the OmniBasic language.
The OmniBasic compiler runs across several platforms, and the programs written for one should compile on the other platforms assuming that you do not have any platform dependencies.
Basic has evolved since the days of line numbers on every line, and this product has evolved too. The OmniBasic language is a “structured” basic language that is mostly backwards compatible with the old, line-numbered programs (just in case you need to run one of those stored on your cassette tape). The language features subroutines and functions with parameters, structured loops, file I/O, built-in string-manipulation routines (RIGHT$, MID$, LEFT$) and math functions. It also has the ability to manipulate pointers and access system functions. For backwards compatibility and for people with poor coding techniques, the language also contains the GOSUB and GOTO statements and supports line numbers.
The language takes the approach of the gnu FORTRAN compiler by converting the BASIC code to C and letting the gnu C compiler finish up the work. As a result, the programs are fast and compact, although not as small as straight C code. The OmniBasic compiler will show the output as C or assembly language, and C code can be mixed with BASIC.
OmniBasic has recently added GUI support using XForms. The beta version I tested worked well, and the release version should be out by the time you read this review. The GUI support is also expected to be cross-platform.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Stunnel Security for Oracle
- SourceClear Open
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Google's SwiftShader Released
- Non-Linux FOSS: Caffeine!
- Parsing an RSS News Feed with a Bash Script
- Doing for User Space What We Did for Kernel Space
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide