handles clause requires a withevents variable
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 5275
MySQL Global User Variables UDF 1.0
MySQL Global User Variables UDF is a MySQL extension to store persistent variables. more>>
MySQL Global User Variables UDF is a MySQL extension to store persistent variables.
This shared library adds simple user functions to MySQL in order to keep persistent shared variables in memory. These variables and their values are available to all clients. Any data can be stored into these persistent variables, including BLOBs. Since updates are atomic and way faster than MEMORY tables, this is an easy and efficient way to handle counters and sequences.
Usage:
Storing a value
An unlimited number of user variables can be created, as long as memory is available.
The GLOBAL_STORE(, ) stores a new shared global variable.
Examples:
mysql> DO GLOBAL_STORE("online_users", 42);
mysql> DO GLOBAL_STORE("secret_key", "pajfUyfnd");
The GLOBAL_STORE() function always returns 1 unless an error occurred.
Fetching a value
Reading the value of a variable is the job of the GLOBAL_GET() function.
The value is returned, or NULL is the variable is undefined.
Example:
mysql> SELECT GLOBAL_GET("online_users;);
42
mysql> SELECT id FROM pxs WHERE secret_key = GLOBAL_GET("secret_key");
1
Atomic increments
A single function call can read the previous value, add an integer (that can be negative), and store the new value into the variable.
The function is GLOBAL_ADD(, ) and the return value is the new value of the variable.
Updates are always atomic, if the old value is 18 and you add 1, you will always get back 19.
Example:
mysql> DO GLOBAL_ADD("online_users", 1);
mysql> SELECT GLOBAL_ADD("online_users", -4);
39
If the value of a variable was a string, the new value is the increment:
mysql> SELECT GLOBAL_ADD("secret_key", 12);
12
Adding a value to an undefined variable returns NULL.
A handy variant is GLOBAL_ADDP(, ). GLOBAL_ADDP() is similar to GLOBAL_ADD() but returns the PREVIOUS value of the variable instead of the new one.
Example:
mysql> DO GLOBAL_SET("xxx", 10);
mysql> SELECT GLOBAL_ADDP("xxx", 1);
10
mysql> SELECT GLOBAL_ADDP("xxx", 1);
11
Installation:
On most systems, compiling and installing the library should be as simple as typing (as root):
make install
The shared library is installed as /usr/local/lib/udf_global_user_variables.so
If the base directory of your MySQL installation is not in /usr/local, just type:
make
and then copy udf_global_user_variables.so to the right location for UDFs on your system (maybe /usr/lib/).
The name of a variable is limited to 256 bytes. If that limit is too low for your specific application, just edit the MAX_NAME_LENGTH variable on top of the .c file and reinstall. Variable names can contain binary characters.
Values are limited to 65536 bytes. If that limit is too low for you, edit the MAX_VALUE_LENGTH variable and reinstall.
<<lessThis shared library adds simple user functions to MySQL in order to keep persistent shared variables in memory. These variables and their values are available to all clients. Any data can be stored into these persistent variables, including BLOBs. Since updates are atomic and way faster than MEMORY tables, this is an easy and efficient way to handle counters and sequences.
Usage:
Storing a value
An unlimited number of user variables can be created, as long as memory is available.
The GLOBAL_STORE(, ) stores a new shared global variable.
Examples:
mysql> DO GLOBAL_STORE("online_users", 42);
mysql> DO GLOBAL_STORE("secret_key", "pajfUyfnd");
The GLOBAL_STORE() function always returns 1 unless an error occurred.
Fetching a value
Reading the value of a variable is the job of the GLOBAL_GET() function.
The value is returned, or NULL is the variable is undefined.
Example:
mysql> SELECT GLOBAL_GET("online_users;);
42
mysql> SELECT id FROM pxs WHERE secret_key = GLOBAL_GET("secret_key");
1
Atomic increments
A single function call can read the previous value, add an integer (that can be negative), and store the new value into the variable.
The function is GLOBAL_ADD(, ) and the return value is the new value of the variable.
Updates are always atomic, if the old value is 18 and you add 1, you will always get back 19.
Example:
mysql> DO GLOBAL_ADD("online_users", 1);
mysql> SELECT GLOBAL_ADD("online_users", -4);
39
If the value of a variable was a string, the new value is the increment:
mysql> SELECT GLOBAL_ADD("secret_key", 12);
12
Adding a value to an undefined variable returns NULL.
A handy variant is GLOBAL_ADDP(, ). GLOBAL_ADDP() is similar to GLOBAL_ADD() but returns the PREVIOUS value of the variable instead of the new one.
Example:
mysql> DO GLOBAL_SET("xxx", 10);
mysql> SELECT GLOBAL_ADDP("xxx", 1);
10
mysql> SELECT GLOBAL_ADDP("xxx", 1);
11
Installation:
On most systems, compiling and installing the library should be as simple as typing (as root):
make install
The shared library is installed as /usr/local/lib/udf_global_user_variables.so
If the base directory of your MySQL installation is not in /usr/local, just type:
make
and then copy udf_global_user_variables.so to the right location for UDFs on your system (maybe /usr/lib/).
The name of a variable is limited to 256 bytes. If that limit is too low for your specific application, just edit the MAX_NAME_LENGTH variable on top of the .c file and reinstall. Variable names can contain binary characters.
Values are limited to 65536 bytes. If that limit is too low for you, edit the MAX_VALUE_LENGTH variable and reinstall.
Download (0.004MB)
Added: 2007-03-19 License: GPL (GNU General Public License) Price:
951 downloads
Pluto Request Action Library 2.0.0.36
Pluto Request Action Library is a library that makes it easy to create a client/server application. more>>
Pluto Request Action Library allows you to create a client/server application, where client sends requests, server replies with responses and optional actions. Very object oriented, and takes only minutes to get going. Same library used for both server & client side.
How does it work?
The client creates "Requests" which it sends to the server. The server will process the request, set some return variables, and can optionally add "Actions" it wants the client to execute in response. An example is a cashiers computer (the client) sends the central credit card processing server a request to "process a credit card", the server responds with the authorization code and also includes an action "give customer a message" which causes a message to appear on the cashiers computer.
Both the client and server use the same library. Both create an instance of RA_Processor.
The only difference is the server calls "ReceiveRequest" and the client creates the actual requests, and calls RA_Processors "SendRequest".
To create a request, just create a class derived from RA_Request. Add some member variables for the request and variables for the response. Your request must be derived from SerializeClass--a base class that facilitates taking an object (a request in this case), serializing the variables into a binary block, and then on the other end reconstructing the class with all the data. The framework handles everything. You just add the data members.
In the above example, the request variables would probably be the credit card information and maybe the customer ID, and the response variables would be the authorization code. RA_Request has a pure virtual function "ProcessRequest" which will be called on the server to handle the request. Both the client and the server have the same Request/Action classes. When the client side passes a request to the RequestProcessor, the framework handles serializing all the request member variables, making the socket connection to the server and sending the request to the server.
On the server, the framework will create an instance of the request class and deserialize all the data and call the "ProcessRequest" member function. That is the only function the server needs to implement. From within ProcessRequest, the server needs to set the response variables. When ProcessRequest returns, the framework will serialize the response variables, send them back to the client, update the clients original request with the response, and execution will continue. Less than 10 lines of code are required to make it work, and the project includes a sample client/server application you can extend.
<<lessHow does it work?
The client creates "Requests" which it sends to the server. The server will process the request, set some return variables, and can optionally add "Actions" it wants the client to execute in response. An example is a cashiers computer (the client) sends the central credit card processing server a request to "process a credit card", the server responds with the authorization code and also includes an action "give customer a message" which causes a message to appear on the cashiers computer.
Both the client and server use the same library. Both create an instance of RA_Processor.
The only difference is the server calls "ReceiveRequest" and the client creates the actual requests, and calls RA_Processors "SendRequest".
To create a request, just create a class derived from RA_Request. Add some member variables for the request and variables for the response. Your request must be derived from SerializeClass--a base class that facilitates taking an object (a request in this case), serializing the variables into a binary block, and then on the other end reconstructing the class with all the data. The framework handles everything. You just add the data members.
In the above example, the request variables would probably be the credit card information and maybe the customer ID, and the response variables would be the authorization code. RA_Request has a pure virtual function "ProcessRequest" which will be called on the server to handle the request. Both the client and the server have the same Request/Action classes. When the client side passes a request to the RequestProcessor, the framework handles serializing all the request member variables, making the socket connection to the server and sending the request to the server.
On the server, the framework will create an instance of the request class and deserialize all the data and call the "ProcessRequest" member function. That is the only function the server needs to implement. From within ProcessRequest, the server needs to set the response variables. When ProcessRequest returns, the framework will serialize the response variables, send them back to the client, update the clients original request with the response, and execution will continue. Less than 10 lines of code are required to make it work, and the project includes a sample client/server application you can extend.
Download (0.37MB)
Added: 2006-02-09 License: GPL (GNU General Public License) Price:
1354 downloads
Language::Basic::Variable 1.44
Language::Basic::Variable is a Perl module to handle parsing and implementing BASIC variables. more>>
Language::Basic::Variable is a Perl module to handle parsing and implementing BASIC variables.
SYNOPSIS
See Language::Basic for the overview of how the Language::Basic module works. This pod page is more technical.
There are two sorts of variables: Arrays and Scalars. Each of those classes has a subclass for Numeric or String variables.
An Array needs to have full LBV::Scalar objects in it, rather than just having an array of values. The reason is that, for example, you might use ARR(3) as the variable in a FOR loop. Also, the "set" and "value" methods apply to a LBV::Scalar (since you cant set an array to a value (in BASIC) so in order to be handle A(3)=3, A(3) needs to be an LBV::Scalar.
The lookup method looks up a variable in the Array or Scalar lookup table (depending on whether there were parentheses after the variable name). BASIC allows undeclared variables, so if the variable name hasnt been seen before, a new variable is created.
Language::Basic::Variable::Scalar class
This class handles a variable or one cell in an array.
Methods include "value", which gets the variables value, and "set", which sets it.
Language::Basic::Variable::Array class
This class handles a BASIC array. Each cell in the array is a LBV::Scalar object.
Methods include "dimension", which dimensions the array to a given size (or a default size) and get_cell, which returns the LBV::Scalar object in a given array location.
Note that BASIC arrays start from 0!
<<lessSYNOPSIS
See Language::Basic for the overview of how the Language::Basic module works. This pod page is more technical.
There are two sorts of variables: Arrays and Scalars. Each of those classes has a subclass for Numeric or String variables.
An Array needs to have full LBV::Scalar objects in it, rather than just having an array of values. The reason is that, for example, you might use ARR(3) as the variable in a FOR loop. Also, the "set" and "value" methods apply to a LBV::Scalar (since you cant set an array to a value (in BASIC) so in order to be handle A(3)=3, A(3) needs to be an LBV::Scalar.
The lookup method looks up a variable in the Array or Scalar lookup table (depending on whether there were parentheses after the variable name). BASIC allows undeclared variables, so if the variable name hasnt been seen before, a new variable is created.
Language::Basic::Variable::Scalar class
This class handles a variable or one cell in an array.
Methods include "value", which gets the variables value, and "set", which sets it.
Language::Basic::Variable::Array class
This class handles a BASIC array. Each cell in the array is a LBV::Scalar object.
Methods include "dimension", which dimensions the array to a given size (or a default size) and get_cell, which returns the LBV::Scalar object in a given array location.
Note that BASIC arrays start from 0!
Download (0.051MB)
Added: 2006-09-29 License: Perl Artistic License Price:
1121 downloads
Regina Rexx Interpreter 3.3
Regina Rexx Interpreter is a portable implementation of the ANSI Standard for Rexx. more>>
Regina is a Rexx interpreter that has been ported to most Unix platforms (Linux, FreeBSD, Solaris, AIX, HP-UX, etc.) and also to OS/2, eCS, DOS, Win9x/Me/NT/2k/XP, Amiga, AROS, QNX4.x, QNX6.x BeOS, MacOS X, EPOC32, AtheOS, OpenVMS, SkyOS and OpenEdition.
Rexx is a programming language that was designed to be easy to use for inexperienced programmers yet powerful enough for experienced users. It is also a language ideally suited as a macro language for other applications.
I am not the author of Regina, but have assumed responsibilities for future maintenance with the full support of the author, Anders Christensen.
There are two major goals for Regina:
- become 100% compliant with the ANSI Standard.
- be available on as many platforms as possible
With the release of Regina 3.1, the first goal has been achieved. Regina now implements all ANSI features, as far as I know. Until an ANSI test suite is available, then youll have to take my word for it.
Enhancements:
- Integration of Florians Generic Call Interface (GCI) into Regina.
- Supported platforms to date are Windows, OS/2 and Linux.
- Fixed bug with TRACE F and its "conversion" into "N" on a subsequent call to TRACE BIF.
- Addition of Polish native language support courtesy of Bartosz Kozlowski.
- PARSE LOWER and PARSE CASELESS added.
- Major changes to EXIT handling
- Regina determines internal and external queues by the fact that external queues MUST have a @ in the name. Therefore any time a queue name is used; in RXQUEUE or ADDRESS...WITH, then if the queue name has a @ then Regina treats this as an external queue, and requires the RXSTACK server to be running.
- New BIF POOLID. Allows the current variable pool number to be obtained (effectively the level of called subroutines).
- VALUE BIF allows environment to be a number corresponding to a variable pool number. Therefore unEXPOSEd variables in any subroutine can be accessed.
- API functions Rexx*Dll() now implemented.
- Locale support for BIFs like TRANSLATE now supported, and can be overridden from command line. (-l switch)
- Algorithm for determining where a Rexx program is (either from command line, or a CALL statement called. Apart from a change in the precedence of directories an environment variable REGINA_SUFFIXES is used to supplement the file extensions that Regina uses to append to the passed file name. More details can be found in the Regina documentation.
- Regina OPTIONS can now be specified as an environment variable, which will set the
- default values for OPTIONS. The OPTIONS instruction can still be used and will override the defaults.
- A new OPTION has been added; CALLS_AS_FUNCS to allow programs that use the non-ANSI format of "CALL label(arg1,arg2)". Although this is implemented as an OPTION, it can only be set via the REGINA_OPTIONS environment variable!
- Another new OPTION; QUEUES_301 to duplicate the behaviour of Regina queues; both
- internal and external.
- Some memory leak fixes with INTERPRET and some "handle leaks" under Windows fixed.
- Initial support for SkyOS
- Fixed some old bugs: (documented in BUGS file) 19991216-29512, 20000319-63722, 36
<<lessRexx is a programming language that was designed to be easy to use for inexperienced programmers yet powerful enough for experienced users. It is also a language ideally suited as a macro language for other applications.
I am not the author of Regina, but have assumed responsibilities for future maintenance with the full support of the author, Anders Christensen.
There are two major goals for Regina:
- become 100% compliant with the ANSI Standard.
- be available on as many platforms as possible
With the release of Regina 3.1, the first goal has been achieved. Regina now implements all ANSI features, as far as I know. Until an ANSI test suite is available, then youll have to take my word for it.
Enhancements:
- Integration of Florians Generic Call Interface (GCI) into Regina.
- Supported platforms to date are Windows, OS/2 and Linux.
- Fixed bug with TRACE F and its "conversion" into "N" on a subsequent call to TRACE BIF.
- Addition of Polish native language support courtesy of Bartosz Kozlowski.
- PARSE LOWER and PARSE CASELESS added.
- Major changes to EXIT handling
- Regina determines internal and external queues by the fact that external queues MUST have a @ in the name. Therefore any time a queue name is used; in RXQUEUE or ADDRESS...WITH, then if the queue name has a @ then Regina treats this as an external queue, and requires the RXSTACK server to be running.
- New BIF POOLID. Allows the current variable pool number to be obtained (effectively the level of called subroutines).
- VALUE BIF allows environment to be a number corresponding to a variable pool number. Therefore unEXPOSEd variables in any subroutine can be accessed.
- API functions Rexx*Dll() now implemented.
- Locale support for BIFs like TRANSLATE now supported, and can be overridden from command line. (-l switch)
- Algorithm for determining where a Rexx program is (either from command line, or a CALL statement called. Apart from a change in the precedence of directories an environment variable REGINA_SUFFIXES is used to supplement the file extensions that Regina uses to append to the passed file name. More details can be found in the Regina documentation.
- Regina OPTIONS can now be specified as an environment variable, which will set the
- default values for OPTIONS. The OPTIONS instruction can still be used and will override the defaults.
- A new OPTION has been added; CALLS_AS_FUNCS to allow programs that use the non-ANSI format of "CALL label(arg1,arg2)". Although this is implemented as an OPTION, it can only be set via the REGINA_OPTIONS environment variable!
- Another new OPTION; QUEUES_301 to duplicate the behaviour of Regina queues; both
- internal and external.
- Some memory leak fixes with INTERPRET and some "handle leaks" under Windows fixed.
- Initial support for SkyOS
- Fixed some old bugs: (documented in BUGS file) 19991216-29512, 20000319-63722, 36
Download (0.61MB)
Added: 2005-04-15 License: LGPL (GNU Lesser General Public License) Price:
1660 downloads
Cell Electrophysiology Simulation Environment 1.4.6
Cell Electrophysiology Simulation Environment is a simulation environment for electrophysiology. more>>
Cell Electrophysiology Simulation Environment (CESE) is a comprehensive framework specifically designed to perform computational electrophysiological simulations, for example, simulations of cardiac myocyte electrical activity.
Cell Electrophysiology Simulation Environment is useful for simulations of action potentials, individual ionic currents, and changes in ionic concentrations.
CESE is a cross-platform program, it runs on any system that has Java runtime environment (JRE) version 1.4 or above. It was tested on Windows, Linux, Solaris, MacOS X, and AIX.
CESE users
CESE is an integrated environment for performing computational simulations using a variety of electrophysiological models.
At this stage CESE allows creation and execution of the single-cell models (containing both Hodgkin-Huxley (HH) and Markovian current formulations). Models of electrical activity of cardiac myocytes with source code are included in the CESE distribution. We hope to extend the number of available models, and add certain neuronal models in the future.
The main strength of CESE is in its uniformity ? a program interface remains the same for different types of models. You can easily switch between models and compare simulation outputs. Model parameters can be modified, selected for output and/or clamped in the same, standard way.
CESE extends the conventional electrophysiological meaning of the "voltage clamp". You can clamp virtually any model variable, including voltage (membrane potential), total or individual ionic currents, ionic concentrations, temperature, gating variables, etc. The clamping commands can be complex piece-wise functions, individually set for the model variable of interest. This opens endless possibilities for the exploration of complex model behavior.
CESE provides simple, but efficient data visualizations. Simulation results can be presented in the graphic and tabulated forms. Plots can be customized, and regions of interest zoomed.
Even though CESE was not designed to be a data analysis tool, you can generate current-voltage relationships (I-Vs) and calculate statistical parameters for a given signal within the program. You can export your data to ASCII, Axon Text File (ATF), and NetCDF formats to continue analysis in your favorite package.
CESE developers
CESE was created from the ground up to incorporate the best programming practices available to Java developers, both in terms of user interface consistency and code clarity and reuse. Wherever possible, CESE rely on available Java APIs (for example Java2D, JavaBeans, JAXP) to simplify the code.
Model creation requires a number of house-keeping functions to be coded ? these include ODE integrators, routines for handling model parameters, saving/restoring model state, visualizing simulation results, etc. CESE provides you with implementation for these routines, hence, you can concentrate on writing the code for concrete ionic current(s), and CESE will handle the rest.
CESE is not trying to create complicated programming frameworks on its own ? rather, it utilizes core Java APIs. For example, models are Java components conforming to the JavaBeans specification. We use XML to specify clamping commands, and Java object serialization to save/restore model parameters.
Enhancements:
- This release improves results printing, adds export to the scalable vector graphics (SVG) format, improves support for continuous simulations, and fixes many bugs in plot rendering and model switching.
<<lessCell Electrophysiology Simulation Environment is useful for simulations of action potentials, individual ionic currents, and changes in ionic concentrations.
CESE is a cross-platform program, it runs on any system that has Java runtime environment (JRE) version 1.4 or above. It was tested on Windows, Linux, Solaris, MacOS X, and AIX.
CESE users
CESE is an integrated environment for performing computational simulations using a variety of electrophysiological models.
At this stage CESE allows creation and execution of the single-cell models (containing both Hodgkin-Huxley (HH) and Markovian current formulations). Models of electrical activity of cardiac myocytes with source code are included in the CESE distribution. We hope to extend the number of available models, and add certain neuronal models in the future.
The main strength of CESE is in its uniformity ? a program interface remains the same for different types of models. You can easily switch between models and compare simulation outputs. Model parameters can be modified, selected for output and/or clamped in the same, standard way.
CESE extends the conventional electrophysiological meaning of the "voltage clamp". You can clamp virtually any model variable, including voltage (membrane potential), total or individual ionic currents, ionic concentrations, temperature, gating variables, etc. The clamping commands can be complex piece-wise functions, individually set for the model variable of interest. This opens endless possibilities for the exploration of complex model behavior.
CESE provides simple, but efficient data visualizations. Simulation results can be presented in the graphic and tabulated forms. Plots can be customized, and regions of interest zoomed.
Even though CESE was not designed to be a data analysis tool, you can generate current-voltage relationships (I-Vs) and calculate statistical parameters for a given signal within the program. You can export your data to ASCII, Axon Text File (ATF), and NetCDF formats to continue analysis in your favorite package.
CESE developers
CESE was created from the ground up to incorporate the best programming practices available to Java developers, both in terms of user interface consistency and code clarity and reuse. Wherever possible, CESE rely on available Java APIs (for example Java2D, JavaBeans, JAXP) to simplify the code.
Model creation requires a number of house-keeping functions to be coded ? these include ODE integrators, routines for handling model parameters, saving/restoring model state, visualizing simulation results, etc. CESE provides you with implementation for these routines, hence, you can concentrate on writing the code for concrete ionic current(s), and CESE will handle the rest.
CESE is not trying to create complicated programming frameworks on its own ? rather, it utilizes core Java APIs. For example, models are Java components conforming to the JavaBeans specification. We use XML to specify clamping commands, and Java object serialization to save/restore model parameters.
Enhancements:
- This release improves results printing, adds export to the scalable vector graphics (SVG) format, improves support for continuous simulations, and fixes many bugs in plot rendering and model switching.
Download (5.0MB)
Added: 2007-02-12 License: GPL (GNU General Public License) Price:
587 downloads
Expresso Framework 5.6
Expresso Framework provides an architectural framework. more>>
Expresso Framework provides an architectural framework.
Expresso Framework is an open standards-based J2EE architectural framework that allows the developer to concentrate on application logic.
It is a library of extensible Java Server application framework components for creating database-driven Web applications based on open standards. Expresso integrates with Apache Jakarta Struts, which emphasizes presentation and application configuration, and bringing a powerful tag library to Expresso.
Expresso adds capabilities for security, robust object-relational mapping, background job handling and scheduling, self-tests, logging integration, automated table manipulation, database connection pooling, email connectivity, event notification, error handling, caching, internationalization, XML automation, testing, registration objects, configuration management, workflow, automatic database maintenance, and a JSP tag library.
Enhancements:
- Move password hash to UserInfo interface and its implementers: password hash no longer in User.java facade, but rather in UserInfo.java interface and its implementers. This allows more flexibility in handling external authentication.
Contributed By: Larry Hamel
- Velocity support for view rendering: Velocity can now be used to render the view. See EDG for details.
Contributed By: David Lloyd
- RunSQL Can Display Table Definitions: Enter the table name in the query section of RunSQL and it will now display the current definition of the underlying database table. Experimental
Contributed By: Michael Rimov
- RunSQL Executes Updates: RunSQL can now execute updates methods as well as select. This allows you to issue ALTER TABLE statements straight through the (secured) web interface. Experimental
Contributed By: Michael Rimov
- Initial Maven integration: Currently has been tested with the site:generate target and the corresponding compile, unittest, etc reports. Not yet used for building distributions. Experimental
Contributed By: Michael Rimov
- RequestRegistry automatically sets data context and security parameters: All calls to setDataContext() will no longer be necessary in client code. This info is propagated using ThreadLocal variables and the "Registry" pattern as described by Martin Fowler. Security parameters (i.e., requesting UID) are also propagated to RowSecuredDBObject, but for the sake of backwards compatibility, they are not propagated to SecuredDBObject. CheckLogin does this work. However, this functionality is also available in a servlet filter, RequestRegistryFilter. If you choose to use RequestRegistryFilter, you could do away with CheckLogin calls from the controller. We would use RequestRegistryFilter everywhere, but legacy installations have various URL paths, each of which requires filtering.
Contributed By: Michael Rimov
- Customizable per-instance UserInfo: Theres a new constructor in User that takes a UserInfo parameter. It allows special behavior for certain users.
Contributed By: Michael Rimov
- New Method: DataObject.setFieldsWithDefaults(): Populates all null fields in the object with default values as specified by the data objects metadata. The behavior mirrors that of DefaultAutoElement.
Contributed By: Michael Rimov.
- revise login bean CurrentLogin to be overridable: revise login bean CurrentLogin to be overridable, as a class handler in expresso-config.xml
Contributed By: Larry Hamel
- Added delimiter attribute to IfMemeberOfGroup tag: If a the delimiter is specified, the groupname will be split on the delimiter. The user will be search for any of the named groups (a logical OR is performed).
Contributed By: Mike Traum
- DataField.isChanged() works after update() and add(): Add method so that DBObject.update() and DBObject.add() can indicate when to cache the current field value as the original value for purposes of isChanged() comparison. Previously, isChanged() was working for DBObject.retrieve() only.
Contributed By: Larry Hamel
- AllowedHtmlPlusURLFilter: AllowedHtmlPlusURLFilter offers the recognition of a limited subset of HTML to be used within an input field. the subset has been chosen to offer some basic formatting without risking Cross site scripting (XSS) dangers.
Contributed By: Larry Hamel
- Struts Validator Integration: Expresso can now use Struts Validator for validating input forms. Rules are defined in validation.xml and validator-rules.xml. See Validating user input in EDG for more details
Contributed By: Raul Davidovich
- new class - com.jcorporate.expresso.core.controller.TilesController: Expresso aware implementation of the org.apache.struts.tiles.Controller interface. This allows for manipulation of theControllerResponse for a particular tile before it is displayed, independantly of the State currently being processed. Developers should extend this class and code the execute() method.
Contributed By: Malcolm Wise
- Various JoinedDataObject enhancements/fixes: You can now specify which fields to retrieve from each dataobject in the join. This list can also include expressions such as SUM(). Added custom WHERE clause facility. Aliases can be used in the custom WHERE clause and these will be translated when the WHERE clause is built. Fixed generation of ON clause when joining tables with a compound key. Provided setConnection() method to facilitate transactioning.
Contributed By: Malcolm Wise
- Stored Procedure support: Now DBObjectos have built in support for database stored procedures
Contributed By: Yves Henri Amaizo
<<lessExpresso Framework is an open standards-based J2EE architectural framework that allows the developer to concentrate on application logic.
It is a library of extensible Java Server application framework components for creating database-driven Web applications based on open standards. Expresso integrates with Apache Jakarta Struts, which emphasizes presentation and application configuration, and bringing a powerful tag library to Expresso.
Expresso adds capabilities for security, robust object-relational mapping, background job handling and scheduling, self-tests, logging integration, automated table manipulation, database connection pooling, email connectivity, event notification, error handling, caching, internationalization, XML automation, testing, registration objects, configuration management, workflow, automatic database maintenance, and a JSP tag library.
Enhancements:
- Move password hash to UserInfo interface and its implementers: password hash no longer in User.java facade, but rather in UserInfo.java interface and its implementers. This allows more flexibility in handling external authentication.
Contributed By: Larry Hamel
- Velocity support for view rendering: Velocity can now be used to render the view. See EDG for details.
Contributed By: David Lloyd
- RunSQL Can Display Table Definitions: Enter the table name in the query section of RunSQL and it will now display the current definition of the underlying database table. Experimental
Contributed By: Michael Rimov
- RunSQL Executes Updates: RunSQL can now execute updates methods as well as select. This allows you to issue ALTER TABLE statements straight through the (secured) web interface. Experimental
Contributed By: Michael Rimov
- Initial Maven integration: Currently has been tested with the site:generate target and the corresponding compile, unittest, etc reports. Not yet used for building distributions. Experimental
Contributed By: Michael Rimov
- RequestRegistry automatically sets data context and security parameters: All calls to setDataContext() will no longer be necessary in client code. This info is propagated using ThreadLocal variables and the "Registry" pattern as described by Martin Fowler. Security parameters (i.e., requesting UID) are also propagated to RowSecuredDBObject, but for the sake of backwards compatibility, they are not propagated to SecuredDBObject. CheckLogin does this work. However, this functionality is also available in a servlet filter, RequestRegistryFilter. If you choose to use RequestRegistryFilter, you could do away with CheckLogin calls from the controller. We would use RequestRegistryFilter everywhere, but legacy installations have various URL paths, each of which requires filtering.
Contributed By: Michael Rimov
- Customizable per-instance UserInfo: Theres a new constructor in User that takes a UserInfo parameter. It allows special behavior for certain users.
Contributed By: Michael Rimov
- New Method: DataObject.setFieldsWithDefaults(): Populates all null fields in the object with default values as specified by the data objects metadata. The behavior mirrors that of DefaultAutoElement.
Contributed By: Michael Rimov.
- revise login bean CurrentLogin to be overridable: revise login bean CurrentLogin to be overridable, as a class handler in expresso-config.xml
Contributed By: Larry Hamel
- Added delimiter attribute to IfMemeberOfGroup tag: If a the delimiter is specified, the groupname will be split on the delimiter. The user will be search for any of the named groups (a logical OR is performed).
Contributed By: Mike Traum
- DataField.isChanged() works after update() and add(): Add method so that DBObject.update() and DBObject.add() can indicate when to cache the current field value as the original value for purposes of isChanged() comparison. Previously, isChanged() was working for DBObject.retrieve() only.
Contributed By: Larry Hamel
- AllowedHtmlPlusURLFilter: AllowedHtmlPlusURLFilter offers the recognition of a limited subset of HTML to be used within an input field. the subset has been chosen to offer some basic formatting without risking Cross site scripting (XSS) dangers.
Contributed By: Larry Hamel
- Struts Validator Integration: Expresso can now use Struts Validator for validating input forms. Rules are defined in validation.xml and validator-rules.xml. See Validating user input in EDG for more details
Contributed By: Raul Davidovich
- new class - com.jcorporate.expresso.core.controller.TilesController: Expresso aware implementation of the org.apache.struts.tiles.Controller interface. This allows for manipulation of theControllerResponse for a particular tile before it is displayed, independantly of the State currently being processed. Developers should extend this class and code the execute() method.
Contributed By: Malcolm Wise
- Various JoinedDataObject enhancements/fixes: You can now specify which fields to retrieve from each dataobject in the join. This list can also include expressions such as SUM(). Added custom WHERE clause facility. Aliases can be used in the custom WHERE clause and these will be translated when the WHERE clause is built. Fixed generation of ON clause when joining tables with a compound key. Provided setConnection() method to facilitate transactioning.
Contributed By: Malcolm Wise
- Stored Procedure support: Now DBObjectos have built in support for database stored procedures
Contributed By: Yves Henri Amaizo
Download (16.2MB)
Added: 2007-02-21 License: The Apache License Price:
977 downloads
Variable::Alias 0.01
Variable::Alias is a Perl module created to alias any variable to any other variable. more>>
Variable::Alias is a Perl module created to alias any variable to any other variable.
SYNOPSIS
use Variable::Alias alias;
my $src;
my $a;
our $b;
my @c;
our @d;
alias $src => $a;
alias $a => $b;
alias $b => $c[0];
alias @c => @d;
$src=src;
# All the other variables now have the string
# src in the appropriate places.
There are various ways to alias one variable to another in Perl. The most popular is by assigning to typeglobs. This is quite efective, but only works with globals. Another method is to use a module like Lexical::Alias or Devel::LexAlias, but as their names suggest, these only work with lexicals. Theres no way to alias an element of an array or hash.
Variable::Alias changes all that. It uses a tie to provide One True Way to alias a variable.
Interface
Variable::Alias may export any or all of five functions. If youve used Lexical::Alias, the interface is virtually identical.
alias(VAR, VAR)
alias takes two variables of any type (scalar, array or hash) and aliases them. Make sure they have the sigil you want on the front.
This function is only available in Perl 5.8.0 and later, because the prototype tricks it uses were first implemented in that version.
alias_s(SCALAR, SCALAR)
alias_s takes two scalars and aliases them.
alias_a(ARRAY, ARRAY)
alias_a takes two arrays and aliases them. Note that this is actual arrays, not array elements, although you can alias references in elements, like so:
alias_a(@short, @{$some->sequence->{of}->calls->{thats}[2]{long}});
alias_h(HASH, HASH)
alias_h takes two hashes and aliases them.
alias_r(REF, REF)
alias_r takes two references and aliases them. The referents must be of the same type.
<<lessSYNOPSIS
use Variable::Alias alias;
my $src;
my $a;
our $b;
my @c;
our @d;
alias $src => $a;
alias $a => $b;
alias $b => $c[0];
alias @c => @d;
$src=src;
# All the other variables now have the string
# src in the appropriate places.
There are various ways to alias one variable to another in Perl. The most popular is by assigning to typeglobs. This is quite efective, but only works with globals. Another method is to use a module like Lexical::Alias or Devel::LexAlias, but as their names suggest, these only work with lexicals. Theres no way to alias an element of an array or hash.
Variable::Alias changes all that. It uses a tie to provide One True Way to alias a variable.
Interface
Variable::Alias may export any or all of five functions. If youve used Lexical::Alias, the interface is virtually identical.
alias(VAR, VAR)
alias takes two variables of any type (scalar, array or hash) and aliases them. Make sure they have the sigil you want on the front.
This function is only available in Perl 5.8.0 and later, because the prototype tricks it uses were first implemented in that version.
alias_s(SCALAR, SCALAR)
alias_s takes two scalars and aliases them.
alias_a(ARRAY, ARRAY)
alias_a takes two arrays and aliases them. Note that this is actual arrays, not array elements, although you can alias references in elements, like so:
alias_a(@short, @{$some->sequence->{of}->calls->{thats}[2]{long}});
alias_h(HASH, HASH)
alias_h takes two hashes and aliases them.
alias_r(REF, REF)
alias_r takes two references and aliases them. The referents must be of the same type.
Download (0.003MB)
Added: 2007-05-04 License: Perl Artistic License Price:
903 downloads
DBIx::Class::Manual::Cookbook 0.08001
DBIx::Class::Manual::Cookbook is a Perl module that contains miscellaneous recipes. more>>
DBIx::Class::Manual::Cookbook is a Perl module that contains miscellaneous recipes.
Paged results
When you expect a large number of results, you can ask DBIx::Class for a paged resultset, which will fetch only a small number of records at a time:
my $rs = $schema->resultset(Artist)->search(
undef,
{
page => 1, # page to return (defaults to 1)
rows => 10, # number of results per page
},
);
return $rs->all(); # all records for page 1
The page attribute does not have to be specified in your search:
my $rs = $schema->resultset(Artist)->search(
undef,
{
rows => 10,
}
);
return $rs->page(1); # DBIx::Class::ResultSet containing first 10 records
In either of the above cases, you can return a Data::Page object for the resultset (suitable for use in e.g. a template) using the pager method:
return $rs->pager();
Complex WHERE clauses
Sometimes you need to formulate a query using specific operators:
my @albums = $schema->resultset(Album)->search({
artist => { like, %Lamb% },
title => { like, %Fear of Fours% },
});
This results in something like the following WHERE clause:
WHERE artist LIKE %Lamb% AND title LIKE %Fear of Fours%
Other queries might require slightly more complex logic:
my @albums = $schema->resultset(Album)->search({
-or => [
-and => [
artist => { like, %Smashing Pumpkins% },
title => Siamese Dream,
],
artist => Starchildren,
],
});
This results in the following WHERE clause:
WHERE ( artist LIKE %Smashing Pumpkins% AND title = Siamese Dream )
OR artist = Starchildren
For more information on generating complex queries, see "WHERE CLAUSES" in SQL::Abstract.
<<lessPaged results
When you expect a large number of results, you can ask DBIx::Class for a paged resultset, which will fetch only a small number of records at a time:
my $rs = $schema->resultset(Artist)->search(
undef,
{
page => 1, # page to return (defaults to 1)
rows => 10, # number of results per page
},
);
return $rs->all(); # all records for page 1
The page attribute does not have to be specified in your search:
my $rs = $schema->resultset(Artist)->search(
undef,
{
rows => 10,
}
);
return $rs->page(1); # DBIx::Class::ResultSet containing first 10 records
In either of the above cases, you can return a Data::Page object for the resultset (suitable for use in e.g. a template) using the pager method:
return $rs->pager();
Complex WHERE clauses
Sometimes you need to formulate a query using specific operators:
my @albums = $schema->resultset(Album)->search({
artist => { like, %Lamb% },
title => { like, %Fear of Fours% },
});
This results in something like the following WHERE clause:
WHERE artist LIKE %Lamb% AND title LIKE %Fear of Fours%
Other queries might require slightly more complex logic:
my @albums = $schema->resultset(Album)->search({
-or => [
-and => [
artist => { like, %Smashing Pumpkins% },
title => Siamese Dream,
],
artist => Starchildren,
],
});
This results in the following WHERE clause:
WHERE ( artist LIKE %Smashing Pumpkins% AND title = Siamese Dream )
OR artist = Starchildren
For more information on generating complex queries, see "WHERE CLAUSES" in SQL::Abstract.
Download (0.28MB)
Added: 2007-06-19 License: Perl Artistic License Price:
860 downloads
WebServerInfo PHP class 1.0.0
WebServerInfo PHP class is intended for developer who create software that will run on different web servers. more>>
WebServerInfo PHP class is intended for developer who create software that will run
on different web servers. The project gives a developer a consistent interface
for accessing web servers variables.
Usage:
You have following options:
Option #1
require_once("WebServerInfo.class.php");
$obj = new WebServerInfo();
print $_SERVER[DOCUMENT_ROOT];
Option #2
require_once("WebServerInfo.class.php");
$obj = new WebServerInfo();
print $obj->get(DOCUMENT_ROOT);
Option #3
uncomment the 3rd line from WebServerInfo.class.php
and all you have to do is require the WebServerInfo.class.php class.
Note:
The constructor of WebServerInfo class overrides $_SERVER variable and
variables can be accessed as usual way.
Following base variables are exported if they do not exist.
REQUEST_URI
REDIRECT_URL
DOCUMENT_ROOT
SERVER_SIGNATURE
SERVER_ADDR
SCRIPT_FILENAME
<<lesson different web servers. The project gives a developer a consistent interface
for accessing web servers variables.
Usage:
You have following options:
Option #1
require_once("WebServerInfo.class.php");
$obj = new WebServerInfo();
print $_SERVER[DOCUMENT_ROOT];
Option #2
require_once("WebServerInfo.class.php");
$obj = new WebServerInfo();
print $obj->get(DOCUMENT_ROOT);
Option #3
uncomment the 3rd line from WebServerInfo.class.php
and all you have to do is require the WebServerInfo.class.php class.
Note:
The constructor of WebServerInfo class overrides $_SERVER variable and
variables can be accessed as usual way.
Following base variables are exported if they do not exist.
REQUEST_URI
REDIRECT_URL
DOCUMENT_ROOT
SERVER_SIGNATURE
SERVER_ADDR
SCRIPT_FILENAME
Download (0.013MB)
Added: 2006-11-22 License: LGPL (GNU Lesser General Public License) Price:
1067 downloads
Mysql Data Manager 1.73
Mysql Data Manager is multifunctional and multiplatform web based mysql administration tool and data editor. more>>
Mysql Data Manager (shortly MDM) is multifunctional and multiplatform web based mysql administration tool and data editor. Mysql Data Manager is a CGI script written in Perl. It uses web browser based GUI, which provides a complete set of high-level and low-level capabilities.
High-level functions allow to accomplish a lot with a single mouse click while low-level functions let you do precisely what you want. Using this tool you get a wide range of solutions to support any Mysql web application.
You log into Mysql server via transparent interface of MDM with no need to store your password into config file. You use all privileges granted to you on Mysql server to manage your databases and accounts. All your mouseclicks are being transmitted to mysql server transparently as a command or a chain of predefined commands.
Almost all messages you may receive from MDM interface are generated natively by mysql server and transparently transferred by MDM to web browser for your convenience.
Mysqk Data Manager is a transparent interface between you and Mysql that helps you to manage your data using pre-programmed operations.
Mysql Data Manager does not require root access to MySQL Server to do all the things you need to as a Database Administrator or Web Administrator through web interface.
Here are some operations that MDM can provide:
- CREATE AND ALTER TABLES. All table types are supported
- DELETE records using WHERE clause. DROP tables
- IMPORT DATA from CSV files generated by other applications.
- EXPORT DATA from search results or entire table into CSV files to use them with other applications.
- EDIT exported CSV FILES
- BACKUP and RESTORE the entire database or selected tables in seconds.
- ACCESS MANAGEMENT - create, edit and delete Mysql user accounts in bulk.
- Manage privileges of single and multiple users on all levels: global, database, table and column.
- SEARCH AND MODIFY records using multiple search criteria. (BLOBs are supported)
- INSERT AND EDIT DATA - edit multiple records from search result, directly or by uploading files from local computer. (unquoted expressions are supported).
- EDIT, INSERT and DELETE records in Spreadsheets
- ZOOM Blob and Text fields
- Visually compose SELECT query, joining several tables.
- PRINT DATA - Generate Printable Output.
- SQL SCRIPTING - Create, save, edit and run SQL scripts and use them as Shortcuts. Multiple queries and comments are supported.
- ADMIN FUNCTIONS - Optimize, Analyze, Repair and Check tables. Show status, Variables etc.
- GENEATE "CREATE TABLE" queries
- Provide each user with dedicated subdirectory to store backups, SQL scripts and exported or uploaded ASCII files.
- Assign maximum total size per user of saved backups, SQL scripts and exported or uploaded ASCII files.
- Customize colors and add clickable image.
- Assign a desired Character Set.
- Set up operational parameters using visual interface.
Main features:
- Security. Mysql Data Manager is as secure as your Mysql Server is. User name and password are not stored in any external file. There is no need to use .htaccess protection.
- Easy installation. Only single file must be uploaded. Setup is done using visual interface. You dont need to be root user to install this Mysql web Client.
- Easy in use. No programming skills are needed. Understandable and intuitive interface.
- Reliability and Efficiency. The program generates only pure HTML code. It does not use client side scripting.
- High Speed. Low Bandwidth. No image is used to build GUI. All you see on the screen is built from standard HTML elements. That means also compatibility with all web browsers.
- Multifunctionality.
- Ability to operate in Multi-User environment as universal control panel for wide range of database applications and services.
- All data types are supported.
- All table types are supported.
- All Mysql versions are supported.
- Ability to preview and customize automatically generated queries.
- Quick Backup and Restore
- Quick Import and Export
- High performance, affordable price.
- User friendly error handling
- Platform independence. This is Perl Script.
- Local connection to databases located on a remote host. Global access over the Internet.
- Fully transparent access to Mysql Server through Perl API.
<<lessHigh-level functions allow to accomplish a lot with a single mouse click while low-level functions let you do precisely what you want. Using this tool you get a wide range of solutions to support any Mysql web application.
You log into Mysql server via transparent interface of MDM with no need to store your password into config file. You use all privileges granted to you on Mysql server to manage your databases and accounts. All your mouseclicks are being transmitted to mysql server transparently as a command or a chain of predefined commands.
Almost all messages you may receive from MDM interface are generated natively by mysql server and transparently transferred by MDM to web browser for your convenience.
Mysqk Data Manager is a transparent interface between you and Mysql that helps you to manage your data using pre-programmed operations.
Mysql Data Manager does not require root access to MySQL Server to do all the things you need to as a Database Administrator or Web Administrator through web interface.
Here are some operations that MDM can provide:
- CREATE AND ALTER TABLES. All table types are supported
- DELETE records using WHERE clause. DROP tables
- IMPORT DATA from CSV files generated by other applications.
- EXPORT DATA from search results or entire table into CSV files to use them with other applications.
- EDIT exported CSV FILES
- BACKUP and RESTORE the entire database or selected tables in seconds.
- ACCESS MANAGEMENT - create, edit and delete Mysql user accounts in bulk.
- Manage privileges of single and multiple users on all levels: global, database, table and column.
- SEARCH AND MODIFY records using multiple search criteria. (BLOBs are supported)
- INSERT AND EDIT DATA - edit multiple records from search result, directly or by uploading files from local computer. (unquoted expressions are supported).
- EDIT, INSERT and DELETE records in Spreadsheets
- ZOOM Blob and Text fields
- Visually compose SELECT query, joining several tables.
- PRINT DATA - Generate Printable Output.
- SQL SCRIPTING - Create, save, edit and run SQL scripts and use them as Shortcuts. Multiple queries and comments are supported.
- ADMIN FUNCTIONS - Optimize, Analyze, Repair and Check tables. Show status, Variables etc.
- GENEATE "CREATE TABLE" queries
- Provide each user with dedicated subdirectory to store backups, SQL scripts and exported or uploaded ASCII files.
- Assign maximum total size per user of saved backups, SQL scripts and exported or uploaded ASCII files.
- Customize colors and add clickable image.
- Assign a desired Character Set.
- Set up operational parameters using visual interface.
Main features:
- Security. Mysql Data Manager is as secure as your Mysql Server is. User name and password are not stored in any external file. There is no need to use .htaccess protection.
- Easy installation. Only single file must be uploaded. Setup is done using visual interface. You dont need to be root user to install this Mysql web Client.
- Easy in use. No programming skills are needed. Understandable and intuitive interface.
- Reliability and Efficiency. The program generates only pure HTML code. It does not use client side scripting.
- High Speed. Low Bandwidth. No image is used to build GUI. All you see on the screen is built from standard HTML elements. That means also compatibility with all web browsers.
- Multifunctionality.
- Ability to operate in Multi-User environment as universal control panel for wide range of database applications and services.
- All data types are supported.
- All table types are supported.
- All Mysql versions are supported.
- Ability to preview and customize automatically generated queries.
- Quick Backup and Restore
- Quick Import and Export
- High performance, affordable price.
- User friendly error handling
- Platform independence. This is Perl Script.
- Local connection to databases located on a remote host. Global access over the Internet.
- Fully transparent access to Mysql Server through Perl API.
Download (0.087MB)
Added: 2006-12-08 License: Free for non-commercial use Price:
1079 downloads
Fedora Package Menu 0.1
Fedora Package Menu is a service menu for easy installation of downloaded RPMs. more>>
Fedora Package Menu is a service menu for easy installation of downloaded RPMs.
Requires sudo and good configuration of sudo.
<<lessRequires sudo and good configuration of sudo.
Download (MB)
Added: 2006-09-20 License: LGPL (GNU Lesser General Public License) Price:
1133 downloads
Sensibe IRC Handler 0.1
Sensible IRC Handler aims to provide an interface for Gaim that handles irc:// links in Firefox Browser. more>>
Sensible IRC Handler aims to provide an interface for Gaim that handles irc:// links in Firefox Browser. This will provide the same xchat-gnome functionality to handle irc:// links, but for Gaim.
Recent changes in inclusion of packages for future Ubuntu release will not include xchat-gnome because of recursive duplication with Gaims IRC capabilities, so IRC will be entirely handled in Gaim.
This will use Gaim as an IRC client, but will not alter the main Gaim configurations, this would create a temporary configurations for the current sessions. A functionality to add the IRC channels defined in InternetRelayChat in Gaim buddy list, will be easy, but will not add them by default. Adding them for a user requires further discussions.
Enhancements:
- GTK+ version 2.2.x
<<lessRecent changes in inclusion of packages for future Ubuntu release will not include xchat-gnome because of recursive duplication with Gaims IRC capabilities, so IRC will be entirely handled in Gaim.
This will use Gaim as an IRC client, but will not alter the main Gaim configurations, this would create a temporary configurations for the current sessions. A functionality to add the IRC channels defined in InternetRelayChat in Gaim buddy list, will be easy, but will not add them by default. Adding them for a user requires further discussions.
Enhancements:
- GTK+ version 2.2.x
Download (0.20MB)
Added: 2006-06-01 License: GPL (GNU General Public License) Price:
1242 downloads
DirHandle 5.8.8
DirHandle is a Perl module created to supply object methods for directory handles. more>>
DirHandle is a Perl module created to supply object methods for directory handles.
SYNOPSIS
use DirHandle;
$d = new DirHandle ".";
if (defined $d) {
while (defined($_ = $d->read)) { something($_); }
$d->rewind;
while (defined($_ = $d->read)) { something_else($_); }
undef $d;
}
The DirHandle method provide an alternative interface to the opendir(), closedir(), readdir(), and rewinddir() functions.
The only objective benefit to using DirHandle is that it avoids namespace pollution by creating globs to hold directory handles.
NOTES
On Mac OS (Classic), the path separator is :, not /, and the current directory is denoted as :, not .. You should be careful about specifying relative pathnames. While a full path always begins with a volume name, a relative pathname should always begin with a :. If specifying a volume name only, a trailing : is required.
<<lessSYNOPSIS
use DirHandle;
$d = new DirHandle ".";
if (defined $d) {
while (defined($_ = $d->read)) { something($_); }
$d->rewind;
while (defined($_ = $d->read)) { something_else($_); }
undef $d;
}
The DirHandle method provide an alternative interface to the opendir(), closedir(), readdir(), and rewinddir() functions.
The only objective benefit to using DirHandle is that it avoids namespace pollution by creating globs to hold directory handles.
NOTES
On Mac OS (Classic), the path separator is :, not /, and the current directory is denoted as :, not .. You should be careful about specifying relative pathnames. While a full path always begins with a volume name, a relative pathname should always begin with a :. If specifying a volume name only, a trailing : is required.
Download (12.2MB)
Added: 2007-05-15 License: Perl Artistic License Price:
895 downloads
AdaControl 1.6r8
AdaControl is a free tool that detects the use of various kinds of constructs in Ada programs. more>>
AdaControl is a free (GMGPL) tool that detects the use of various kinds of constructs in Ada programs. AdaControls first goal is to control proper usage of style or programming rules, but it can also be used as a powerful tool to search for use (or non-use) of various forms of programming styles or design patterns. Searched elements range from very simple, like the occurrence of certaine entities, declarations, or statements, to very sophisticated, like verifying that certain programming patterns are being obeyed..
Which elements or constructs are searched is defined by a set of rules; the following table gives a short summary of rules currently checked by AdaControl. The number in parentheses after the rule name gives the number of subrules, if any. Considering all possible rules and subrules, this makes 216 tests that can be performed currently by AdaControl!
- Abnormal_Function_Return Controls a design pattern that ensures that a function always returns a result .
- Allocators Controls ocurrences of allocators, either all of them, or those targeting specified types.
- Array_Declarations (x2) Controls several metrics in array declarations.
- Barrier_Expressions Controls elements allowed in the expression of protected entries barriers
- Case_Statement (x4) Controls several metrics in case statements.
- Control_Characters Controls occurrences of control characters (like tabs) in the source.
- Declarations (x75) Controls occurrences of certain Ada declarations.
- Default_Parameter Controls subprogram calls and generic instantiations that use (or not) the default value for a given parameter.
- Directly_Accessed_Globals Controls a design pattern that ensures that all global variables are accessed only through dedicated subprograms.
- Entities Controls occurrences of any Ada entity.
- Entity_Inside_Exception Controls occurrences of entities inside exception handlers.
- Exception_Propagation (x4) Controls that certain subprograms (or tasks) cannot propagate exceptions, or that no elaboration can propagate exceptions.
- Expressions (x9) Controls usage of certain forms of expressions
- Global_References Controls unsynchronized accesses to global variables.
- Header_Comments (x2) Controls the presence of comments at the start of each module.
- If_For_Case Controls if statements that could be replaced by case statements.
- Instantiations Controls generic instantiations, either all of them, or those that use specified entities.
- Insufficient_Parameters Controls the use of positional parameters in calls where the value does not provide sufficient information.
- Local_Hiding Controls occurrences of local identifiers that hide an identical outer one.
- Local_Instantiation Controls instantiations in local scopes.
- Max_Blank_Lines Controls the occurrence of more than a specified number of consecutive empty lines.
- Max_Call_Depth Controls the maximum depth of subprogram calls.
- Max_Line_Length Controls maximal length of source lines.
- Max_Nesting Controls scopes nested more deeply than a given limit.
- Max_Parameters (x6) Controls the maximum numbers of parameters in callable entities (procedures, functions and entries)
- Max_Statement_Nesting (x5) Controls composite statements nested more deeply than a given limit.
- Movable_Accept_Statements Controls statements that could be moved outside an accept statement.
- Naming_Convention Controls the form of allowed (or forbidden) names in declarations.
- No_Safe_Initialization Controls a design pattern that ensures that any variable is initialized before being used.
- Non_Static (x3) Controls non static expressions in index or discriminant constraints, or in instantiations.
- Not_Elaboration_Calls Controls subprogram calls performed from places outside package elaboration code.
- Other_Dependencies Controls semantic dependencies to other units than those indicated
- Parameter_Aliasing Controls subprograms and entry calls where a variable is provided to more than one [in] out parameter.
- Potentially_Blocking_Operations Controls the use of potentially blocking operations from within protected operations.
- Pragmas Controls the use of specific pragmas.
- Real_Operators Controls occurrences of = or /= operators on real types.
- Reduceable_Scope Controls declarations that could be move to more deeply nested scopes.
- Representation_Clauses Controls occurrences of representation clauses.
- Return_Type Controls the use of certain kinds of types as return types of functions.
- Side_Effect_Parameters Controls subprogram calls and generic instantiations that call functions with side effect, thus creating a dependance to the order of evaluation.
- Silent_Exceptions Controls exception handlers that do not reraise exceptions nor call indicated subprograms.
- Simplifiable_Expressions (x4) Controls occurrences of various forms of expressions that could be simplified.
- Special_Comments Controls the presence of certain string patterns in comments.
- Statements (x42) Controls occurrences of Ada statements.
- Style (x12) Controls various forms of constructs generally recommended in style rules.
- Terminating_Tasks Controls a design pattern that ensures that tasks never terminate.
- Uncheckable (x3) Controls constructs that are not statically checkable by other rules
- Unnecessary_Use_Clause Controls use clauses on packages, where no element of the package is referred to within the scope of the use clause.
- Unsafe_Paired_Calls Controls a design pattern that ensures that certain calls are allways paired (like P/V procedures).
- Unsafe_Unchecked_Conversion Controls instantiations of Unchecked_Conversion between types of different or unspecified sizes.
- Usage (x5) Controls usage of objects under certain conditions (in package specifications, read, written modified...).
- Use_Clauses Controls occurrences of use clauses, except for indicated packages.
- With_Clauses (x3) Controls proper usage of with clauses.
Enhancements:
- This release adds rules to check that header comments match a given pattern.
- It has indication of possible false positives and false negatives due to non-statically analyzable constructs.
- There is a fine definition of constructs allowed in entry barriers (including the one of the Ravenscar profile).
- There is better integration into GPS, and much more.
<<lessWhich elements or constructs are searched is defined by a set of rules; the following table gives a short summary of rules currently checked by AdaControl. The number in parentheses after the rule name gives the number of subrules, if any. Considering all possible rules and subrules, this makes 216 tests that can be performed currently by AdaControl!
- Abnormal_Function_Return Controls a design pattern that ensures that a function always returns a result .
- Allocators Controls ocurrences of allocators, either all of them, or those targeting specified types.
- Array_Declarations (x2) Controls several metrics in array declarations.
- Barrier_Expressions Controls elements allowed in the expression of protected entries barriers
- Case_Statement (x4) Controls several metrics in case statements.
- Control_Characters Controls occurrences of control characters (like tabs) in the source.
- Declarations (x75) Controls occurrences of certain Ada declarations.
- Default_Parameter Controls subprogram calls and generic instantiations that use (or not) the default value for a given parameter.
- Directly_Accessed_Globals Controls a design pattern that ensures that all global variables are accessed only through dedicated subprograms.
- Entities Controls occurrences of any Ada entity.
- Entity_Inside_Exception Controls occurrences of entities inside exception handlers.
- Exception_Propagation (x4) Controls that certain subprograms (or tasks) cannot propagate exceptions, or that no elaboration can propagate exceptions.
- Expressions (x9) Controls usage of certain forms of expressions
- Global_References Controls unsynchronized accesses to global variables.
- Header_Comments (x2) Controls the presence of comments at the start of each module.
- If_For_Case Controls if statements that could be replaced by case statements.
- Instantiations Controls generic instantiations, either all of them, or those that use specified entities.
- Insufficient_Parameters Controls the use of positional parameters in calls where the value does not provide sufficient information.
- Local_Hiding Controls occurrences of local identifiers that hide an identical outer one.
- Local_Instantiation Controls instantiations in local scopes.
- Max_Blank_Lines Controls the occurrence of more than a specified number of consecutive empty lines.
- Max_Call_Depth Controls the maximum depth of subprogram calls.
- Max_Line_Length Controls maximal length of source lines.
- Max_Nesting Controls scopes nested more deeply than a given limit.
- Max_Parameters (x6) Controls the maximum numbers of parameters in callable entities (procedures, functions and entries)
- Max_Statement_Nesting (x5) Controls composite statements nested more deeply than a given limit.
- Movable_Accept_Statements Controls statements that could be moved outside an accept statement.
- Naming_Convention Controls the form of allowed (or forbidden) names in declarations.
- No_Safe_Initialization Controls a design pattern that ensures that any variable is initialized before being used.
- Non_Static (x3) Controls non static expressions in index or discriminant constraints, or in instantiations.
- Not_Elaboration_Calls Controls subprogram calls performed from places outside package elaboration code.
- Other_Dependencies Controls semantic dependencies to other units than those indicated
- Parameter_Aliasing Controls subprograms and entry calls where a variable is provided to more than one [in] out parameter.
- Potentially_Blocking_Operations Controls the use of potentially blocking operations from within protected operations.
- Pragmas Controls the use of specific pragmas.
- Real_Operators Controls occurrences of = or /= operators on real types.
- Reduceable_Scope Controls declarations that could be move to more deeply nested scopes.
- Representation_Clauses Controls occurrences of representation clauses.
- Return_Type Controls the use of certain kinds of types as return types of functions.
- Side_Effect_Parameters Controls subprogram calls and generic instantiations that call functions with side effect, thus creating a dependance to the order of evaluation.
- Silent_Exceptions Controls exception handlers that do not reraise exceptions nor call indicated subprograms.
- Simplifiable_Expressions (x4) Controls occurrences of various forms of expressions that could be simplified.
- Special_Comments Controls the presence of certain string patterns in comments.
- Statements (x42) Controls occurrences of Ada statements.
- Style (x12) Controls various forms of constructs generally recommended in style rules.
- Terminating_Tasks Controls a design pattern that ensures that tasks never terminate.
- Uncheckable (x3) Controls constructs that are not statically checkable by other rules
- Unnecessary_Use_Clause Controls use clauses on packages, where no element of the package is referred to within the scope of the use clause.
- Unsafe_Paired_Calls Controls a design pattern that ensures that certain calls are allways paired (like P/V procedures).
- Unsafe_Unchecked_Conversion Controls instantiations of Unchecked_Conversion between types of different or unspecified sizes.
- Usage (x5) Controls usage of objects under certain conditions (in package specifications, read, written modified...).
- Use_Clauses Controls occurrences of use clauses, except for indicated packages.
- With_Clauses (x3) Controls proper usage of with clauses.
Enhancements:
- This release adds rules to check that header comments match a given pattern.
- It has indication of possible false positives and false negatives due to non-statically analyzable constructs.
- There is a fine definition of constructs allowed in entry barriers (including the one of the Ravenscar profile).
- There is better integration into GPS, and much more.
Download (1.0MB)
Added: 2006-12-08 License: GMGPL (GNAT Modified GPL) Price:
1050 downloads
PHP MySQL Database Layer Class 1.03
PHP MySQL Database Layer Class is a php class providing some very useful methods to work with a mySQL database. more>>
PHP MySQL Database Layer Class is a php class providing some very useful methods to work with a mySQL database.
Main features:
- connects you to a mySQL host and select a database in a single call (opposed to PHPs native functions which requires two steps)
- has a "query" method that has the same role as PHPs mysql_query but this one will tell you about the affected rows (through the "affectedRows" property) when executing an INSERT, UPDATE, DELETE query and about the found rows (through the "foundRows" property) when executing a SELECT query - the "foundRows" property tells you how many records would the query return if there was no LIMIT applied to it - very useful when creating listing so you dont have to do a query to determine how many records you have in a database and the again a query to show only the records from a page
- has an "escape_string" method that will "mysql_real_escape_string" your string weather the magic_quotes are on or not
- has a "dlookup" method that i am sure you will find VERY useful once you get to know it: it return data from a single table cell based on standard mySQL WHERE criteria - see the manual for detailed info! (yes, it acts exactly like the function with the same name from microsft access)
- provides you with a very useful debug interface which shows you each query your script is running, for how long, the total number of queries made, the total execution time of your queries, errors of your queries and what are the values of $_GET, $_POST, $_COOKIES and $_SERVER superglobal variables. The debug interface is template driven and supports localisation.
- it will notify you if a specific query is executed more than once and will advise you to optimize the script
- you can instruct it to send you an email if a query runs longer then a specified time
- the code is heavily documented so you can easily understand every aspect of it and even maybe use it as a php tutorial
Enhancements:
- the state of $_FILES and $_SESSION superglobals are now also shown in the debug window
- better integration with XTemplate (previously, there was a variable assigned to each entry in the language file now the XTemplates feature to handle arrays is used)
- properties will now have default values in PHP 4
<<lessMain features:
- connects you to a mySQL host and select a database in a single call (opposed to PHPs native functions which requires two steps)
- has a "query" method that has the same role as PHPs mysql_query but this one will tell you about the affected rows (through the "affectedRows" property) when executing an INSERT, UPDATE, DELETE query and about the found rows (through the "foundRows" property) when executing a SELECT query - the "foundRows" property tells you how many records would the query return if there was no LIMIT applied to it - very useful when creating listing so you dont have to do a query to determine how many records you have in a database and the again a query to show only the records from a page
- has an "escape_string" method that will "mysql_real_escape_string" your string weather the magic_quotes are on or not
- has a "dlookup" method that i am sure you will find VERY useful once you get to know it: it return data from a single table cell based on standard mySQL WHERE criteria - see the manual for detailed info! (yes, it acts exactly like the function with the same name from microsft access)
- provides you with a very useful debug interface which shows you each query your script is running, for how long, the total number of queries made, the total execution time of your queries, errors of your queries and what are the values of $_GET, $_POST, $_COOKIES and $_SERVER superglobal variables. The debug interface is template driven and supports localisation.
- it will notify you if a specific query is executed more than once and will advise you to optimize the script
- you can instruct it to send you an email if a query runs longer then a specified time
- the code is heavily documented so you can easily understand every aspect of it and even maybe use it as a php tutorial
Enhancements:
- the state of $_FILES and $_SESSION superglobals are now also shown in the debug window
- better integration with XTemplate (previously, there was a variable assigned to each entry in the language file now the XTemplates feature to handle arrays is used)
- properties will now have default values in PHP 4
Download (0.067MB)
Added: 2006-09-08 License: Free for non-commercial use Price:
678 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above handles clause requires a withevents variable search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
