With the release of Xbase++ Build#2187, new features such as SmartOrders and RemoteFilters have been introduced, bringing significant changes to how ISAM-compatible orders are implemented. As a software developer working with Xbase++, it's a good idea to understand these changes, especially when...
When working with databases, one of the most critical and costly tasks developers face is data model maintenance. The ease with which data structures can be managed can make a significant difference in the amount of time and effort developers spend. In this article, we will examine the...
Background
Generally making a service more reliable does not mean to ensure the service works 24/7. This is an old school no more working approach from times where software solutions have been simple, working in defined environments and under full control. But today, even simple software become...
Comments for Xbase++ 1.9 users
1. Support for projects with targets in multiple directories
Beginning with Xbase++ version 2.0, complex project scenarios involving targets located in different directories are fully supported. This required changes in the way the targets and the source files...
Xbase++ provides INIT procedures, a concepts which allows by a simple declaration of INIT before the procedure keyword to ensure that this procedure is executed before your procedure main is executed. An example is shown below.
INIT PROCEDURE startupMyModule()
// your code is
RETURN...
By default the Xbase++ WebHandler does negotiate the content type encoding automatically. The following simple AddressService returns a Object and leaves the content negotiation up to the WebHandler and the request sending party. The great benefit of that approach is that your service interfaces...
Overview
With associative arrays it is possible to address an element in the array not by its ordinal (numeric) but by name (character string). The Xbase++ datatype array does not support this possibility.
However, objects of the class DataObject() semantically offer an identical usage, because...
Rules:
Avoid the need for comments, write clear, readable and self describing code instead
Comments never describe the code and its syntax
Use comments to compensate for your failure to express yourself in code properly.
Do not write informative comments such as:
// returns normalized value...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.