macro
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 286
Ooo-macro 2.2en
ooo-macro is a toolkit for OpenOffice.org or StarOffice. more>>
Ooo-macro is a toolkit for OpenOffice.org or StarOffice including macros written in StarBasic, associated shortcuts, the template SPECIAL.stw, and the Perl script.
It is a complete kit of macros and shortcuts for everyday usage of StarWriter and OpenOffice.org Writer. (English version.)
Enhancements:
- This release includes a shell script and a Midnight Commander plug-in for fast dumping and viewing of the contents of OpenOffice.org 2.x ODT and ODS files and version 1.x SXW and SXC files.
<<lessIt is a complete kit of macros and shortcuts for everyday usage of StarWriter and OpenOffice.org Writer. (English version.)
Enhancements:
- This release includes a shell script and a Midnight Commander plug-in for fast dumping and viewing of the contents of OpenOffice.org 2.x ODT and ODS files and version 1.x SXW and SXC files.
Download (0.095MB)
Added: 2005-10-19 License: GPL (GNU General Public License) Price:
1473 downloads
XMacroj 0.1.0
XMacroJ is an XML macro language for building text documents from XML components. more>>
XMacroJ is an XML macro language for building text documents from XML components. The project removes the reliance on using the include directives and frees the programmer from locking the development directly into a specific framework.
Using XMacroJ, the developer can loosely couple the development process to a framework by developing macros that wrap the framework and then creating target documents that are based on the macros.
If the developer chooses to use a different framework, then only the macros are changed and the target documents can be recompiled.
Build:
1. You must have Apache ant installed.
2. Edit the build.properties file and update the mainbuild path to your desired
directory
3. Just run ant in the directory that contains the ant build.xml file
The build directory will contain the compiled jar. You will need to link this into ant if you wish to use the com.embsoft.tools.xml.macro.XMacroAnt task.
See the doc/doc.txt for details on how to use the xml macro language
Enhancements:
- Insertions functionality was added.
- Insertions allow XML macros to insert into multiple streams which are then concatenated together in the target destination file.
- For example, you could use an insertion in a macro to insert an include directive in an XHTML document header element, or an import line when generating a Java file.
<<lessUsing XMacroJ, the developer can loosely couple the development process to a framework by developing macros that wrap the framework and then creating target documents that are based on the macros.
If the developer chooses to use a different framework, then only the macros are changed and the target documents can be recompiled.
Build:
1. You must have Apache ant installed.
2. Edit the build.properties file and update the mainbuild path to your desired
directory
3. Just run ant in the directory that contains the ant build.xml file
The build directory will contain the compiled jar. You will need to link this into ant if you wish to use the com.embsoft.tools.xml.macro.XMacroAnt task.
See the doc/doc.txt for details on how to use the xml macro language
Enhancements:
- Insertions functionality was added.
- Insertions allow XML macros to insert into multiple streams which are then concatenated together in the target destination file.
- For example, you could use an insertion in a macro to insert an include directive in an XHTML document header element, or an import line when generating a Java file.
Download (0.085MB)
Added: 2006-11-17 License: LGPL (GNU Lesser General Public License) Price:
1072 downloads
HTML::Macro 1.27
HTML::Macro can process HTML templates with loops, conditionals, macros and more! more>>
HTML::Macro can process HTML templates with loops, conditionals, macros and more!
SYNOPSIS
use HTML::Macro;
$htm = new HTML::Macro (template.html);
$htm->print;
sub myfunc {
$htm->declare (var, missing);
$htm->set (var, value);
return $htm->process;
}
( in template.html ):
< html >< body >
< eval expr="&myfunc" >
< if def="missing" >
Message about missing stuff...
< else / >
Vars value is #var#.
< /if >
< /eval >
< /body >< /html >
HTML::Macro is a module to be used behind a web server (in CGI scripts). It provides a convenient mechanism for generating HTML pages by combining "dynamic" data derived from a database or other computation with HTML templates that represent fixed or "static" content of a page.
There are many different ways to accomplish what HTML::Macro does, including ASP, embedded perl, CFML, etc, etc. The motivation behind HTML::Macro is to keep everything that a graphic designer wants to play with *in a single HTML template*, and to keep as much as possible of what a perl programmer wants to play with *in a perl file*. Our thinking is that there are two basically dissimilar tasks involved in producing a dynamic web page: graphic design and programming. Even if one person is responsible for both tasks, it is useful to separate them in order to aid clear thinking and organized work. I guess you could say the main motivation for this separation is to make it easier for emacs (and other text processors, including humans) to parse your files: its yucky to have a lot of HTML in a string in your perl file, and its yucky to have perl embedded in a special tag in an HTML file.
HTML::Macro began with some simple programming constructs: macro expansions, include files, conditionals, loops and block quotes. Since then weve added very little: only a define tag to allow setting values and an eval tag to allow perl function calls in a nested macro scope. Our creed is "less is more, more or less."
HTML::Macro variables will look familiar to C preprocessor users or especially to Cold Fusion people. They are always surrounded with single or double hash marks: "#" or "##". Variables surrounded by double hash marks are subject to html entity encoding; variables with single hash marks are substituted "as is" (like single quotes in perl or UNIX shells). Conditionals are denoted by the and tags, and loops by the tag. Quoting used to be done using a tag, but we now deprecate that in favor of the more familiar CFML quoting syntax: < !--- --- >.
<<lessSYNOPSIS
use HTML::Macro;
$htm = new HTML::Macro (template.html);
$htm->print;
sub myfunc {
$htm->declare (var, missing);
$htm->set (var, value);
return $htm->process;
}
( in template.html ):
< html >< body >
< eval expr="&myfunc" >
< if def="missing" >
Message about missing stuff...
< else / >
Vars value is #var#.
< /if >
< /eval >
< /body >< /html >
HTML::Macro is a module to be used behind a web server (in CGI scripts). It provides a convenient mechanism for generating HTML pages by combining "dynamic" data derived from a database or other computation with HTML templates that represent fixed or "static" content of a page.
There are many different ways to accomplish what HTML::Macro does, including ASP, embedded perl, CFML, etc, etc. The motivation behind HTML::Macro is to keep everything that a graphic designer wants to play with *in a single HTML template*, and to keep as much as possible of what a perl programmer wants to play with *in a perl file*. Our thinking is that there are two basically dissimilar tasks involved in producing a dynamic web page: graphic design and programming. Even if one person is responsible for both tasks, it is useful to separate them in order to aid clear thinking and organized work. I guess you could say the main motivation for this separation is to make it easier for emacs (and other text processors, including humans) to parse your files: its yucky to have a lot of HTML in a string in your perl file, and its yucky to have perl embedded in a special tag in an HTML file.
HTML::Macro began with some simple programming constructs: macro expansions, include files, conditionals, loops and block quotes. Since then weve added very little: only a define tag to allow setting values and an eval tag to allow perl function calls in a nested macro scope. Our creed is "less is more, more or less."
HTML::Macro variables will look familiar to C preprocessor users or especially to Cold Fusion people. They are always surrounded with single or double hash marks: "#" or "##". Variables surrounded by double hash marks are subject to html entity encoding; variables with single hash marks are substituted "as is" (like single quotes in perl or UNIX shells). Conditionals are denoted by the and tags, and loops by the tag. Quoting used to be done using a tag, but we now deprecate that in favor of the more familiar CFML quoting syntax: < !--- --- >.
Download (0.023MB)
Added: 2006-07-31 License: Perl Artistic License Price:
1180 downloads
Text::Macro 0.07
Text::Macro Perl module is a template facility whos focus is on generating code such as c, java or sql. more>>
Text::Macro Perl module is a template facility whos focus is on generating code such as c, java or sql. While generating perl code is also possible, there is a potential conflict between the control-symbol and the perl comment symbol.
Perl is excelent at manipulating text, and it begs the question why one would need such a tool.
The answer is that good code design should be such that applications should not have to be modified so as to make configuration changes. Thus external configuration files/data is used. However, if these files are read in as perl-code, then simple errors could crash the whole application (or provide subtle security risks). Further, it is often desired to invert the control flow and text-data (namely, make the embedded strings primary, and control-flow secondary). This is the ASP model, and for 90% HTML, 10% code, this works great.
This module supports many control facilities which directly translate into perl-control facilities (e.g. inverting the ASP-style code back into perl-style behind the scenes). The inversion process is cached in a simple user object.
The module was initially inspired by Text::FastTemplate by Robert Lehr, whos module didnt completely fullfill my needs.
Main features:
- fast, simple, robust
- code-generating-centric feature-set
- substitutions stand-out from template
- macro-code embedded in text
- OOP
- external and internal includes (for clearifying complex control-flow)
- scoped variable-substitutions
- line-based processing (like cpp)
- usable error messages
<<lessPerl is excelent at manipulating text, and it begs the question why one would need such a tool.
The answer is that good code design should be such that applications should not have to be modified so as to make configuration changes. Thus external configuration files/data is used. However, if these files are read in as perl-code, then simple errors could crash the whole application (or provide subtle security risks). Further, it is often desired to invert the control flow and text-data (namely, make the embedded strings primary, and control-flow secondary). This is the ASP model, and for 90% HTML, 10% code, this works great.
This module supports many control facilities which directly translate into perl-control facilities (e.g. inverting the ASP-style code back into perl-style behind the scenes). The inversion process is cached in a simple user object.
The module was initially inspired by Text::FastTemplate by Robert Lehr, whos module didnt completely fullfill my needs.
Main features:
- fast, simple, robust
- code-generating-centric feature-set
- substitutions stand-out from template
- macro-code embedded in text
- OOP
- external and internal includes (for clearifying complex control-flow)
- scoped variable-substitutions
- line-based processing (like cpp)
- usable error messages
Download (0.012MB)
Added: 2007-05-31 License: Perl Artistic License Price:
877 downloads
mod_macro 1.1.7
mod_macro is a third-party module to the Apache Http Server, distributed with a BSD-style license like Apache. more>>
mod_macro is a third-party module to the Apache Http Server, distributed with a BSD-style license like Apache.
mod_macro allows the definition and use of macros within apache runtime configuration files. The syntax is a natural extension to apache html-like configuration style.
Examples
Here is a sample use of mod_macro within a configuration file:
## Define a VHost Macro.
< Macro VHost $host $port $dir >
Listen $port
< VirtualHost $host:$port >
DocumentRoot $dir
< Directory $dir >
# do something here...
< /Directory >
# limit access to intranet subdir.
< Directory $dir/intranet >
order deny,allow
deny from all
allow from 10.0.0.0/8
< /Directory >
< /VirtualHost >
< /Macro >
## Use of VHost with different arguments.
Use VHost www.apache.org 80 /projects/apache/web
Use VHost www.perl.com 8080 /projects/perl/web
Use VHost www.ensmp.fr 1234 /projects/mines/web
## Done.
<<lessmod_macro allows the definition and use of macros within apache runtime configuration files. The syntax is a natural extension to apache html-like configuration style.
Examples
Here is a sample use of mod_macro within a configuration file:
## Define a VHost Macro.
< Macro VHost $host $port $dir >
Listen $port
< VirtualHost $host:$port >
DocumentRoot $dir
< Directory $dir >
# do something here...
< /Directory >
# limit access to intranet subdir.
< Directory $dir/intranet >
order deny,allow
deny from all
allow from 10.0.0.0/8
< /Directory >
< /VirtualHost >
< /Macro >
## Use of VHost with different arguments.
Use VHost www.apache.org 80 /projects/apache/web
Use VHost www.perl.com 8080 /projects/perl/web
Use VHost www.ensmp.fr 1234 /projects/mines/web
## Done.
Download (0.013MB)
Added: 2006-05-08 License: BSD License Price:
1264 downloads
Filter::Macro 0.11
Filter::Macro is a Perl module to make macro modules that are expanded inline. more>>
Filter::Macro is a Perl module to make macro modules that are expanded inline.
SYNOPSIS
In MyHandyModules.pm:
package MyHandyModules;
use Filter::Macro;
# lines below will be expanded into callers code
use strict;
use warnings;
use Switch;
use IO::All;
use Quantum::Superpositions;
In your program or module:
use MyHandyModules; # lines above are expanded here
If many of your programs begin with the same lines, it may make sense to abstract them away into a module, and use that module instead.
Sadly, it does not work that way, because by default, all lexical pragmas, source filters and subroutine imports invoked in MyHandyModules.pm takes effect in that module, not the calling programs.
One way to solve this problem is to use Filter::Include:
use Filter::Include;
include MyHandyModules;
However, it would be really nice if MyHandyModules.pm could define the macro-like semantic itself, instead of placing the burden on the caller.
This module lets you do precisely that. All you need to do is to put one line in MyHandyModules.pm, after the package MyHandyModules; line:
use Filter::Macro;
With this, a program or module that says use Filter::Macro will expand lines below use Filter::Macro into their own code, instead of the default semantic of evaluating them in the MyHandyModules package.
Line numbers in error and warning messages are unaffected by this module; they still point to the correct file name and line numbers.
<<lessSYNOPSIS
In MyHandyModules.pm:
package MyHandyModules;
use Filter::Macro;
# lines below will be expanded into callers code
use strict;
use warnings;
use Switch;
use IO::All;
use Quantum::Superpositions;
In your program or module:
use MyHandyModules; # lines above are expanded here
If many of your programs begin with the same lines, it may make sense to abstract them away into a module, and use that module instead.
Sadly, it does not work that way, because by default, all lexical pragmas, source filters and subroutine imports invoked in MyHandyModules.pm takes effect in that module, not the calling programs.
One way to solve this problem is to use Filter::Include:
use Filter::Include;
include MyHandyModules;
However, it would be really nice if MyHandyModules.pm could define the macro-like semantic itself, instead of placing the burden on the caller.
This module lets you do precisely that. All you need to do is to put one line in MyHandyModules.pm, after the package MyHandyModules; line:
use Filter::Macro;
With this, a program or module that says use Filter::Macro will expand lines below use Filter::Macro into their own code, instead of the default semantic of evaluating them in the MyHandyModules package.
Line numbers in error and warning messages are unaffected by this module; they still point to the correct file name and line numbers.
Download (0.013MB)
Added: 2007-02-20 License: MIT/X Consortium License Price:
976 downloads
Text::MacroScript 1.38
Text::MacroScript is a macro pre-processor with embedded perl capability. more>>
Text::MacroScript is a macro pre-processor with embedded perl capability.
SYNOPSIS
use Text::MacroScript ;
# new() for macro processing
my $Macro = Text::MacroScript->new ;
while( ) {
print $Macro->expand( $_ ) if $_ ;
}
# Canonical use (the filename improves error messages):
my $Macro = Text::MacroScript->new ;
while( ) {
print $Macro->expand( $_, $ARGV ) if $_ ;
}
# new() for embedded macro processing
my $Macro = Text::MacroScript->new( -embedded => 1 ) ;
# Delimiters default to
# or
my $Macro = Text::MacroScript->new( -opendelim => [[, -closedelim => ]] ) ;
while( ) {
print $Macro->expand_delimited( $_, $ARGV ) if $_ ;
}
# Create a macro object and create initial macros/scripts from the file(s)
# given:
my $Macro = Text::MacroScript->new(
-file => [ local.macro, ~/.macro/global.macro ]
) ;
# Create a macro object and create initial macros/scripts from the
# definition(s) given:
my $Macro = Text::MacroScript->new(
-macro => [
[ MAX_INT => 32767 ],
],
-script => [
[ DHM2S =>
[
my $s = (#0*24*60*60)+(#1*60*60)+(#2*60) ;
"#0 days, #1 hrs, #2 mins = $s secs"
],
],
-variable => [ *MARKER* => 0 ],
) ;
# We may of course use any combination of the options.
my $Macro = Text::MacroScript->new( -comment => 1 ) ; # Create the %%[] macro.
# define()
$Macro->define( -macro, $macroname, $macrobody ) ;
$Macro->define( -script, $scriptname, $scriptbody ) ;
$Macro->define( -variable, $variablename, $variablebody ) ;
# undefine()
$Macro->undefine( -macro, $macroname ) ;
$Macro->undefine( -script, $scriptname ) ;
$Macro->undefine( -variable, $variablename ) ;
# undefine_all()
$Macro->undefine( -macro ) ;
$Macro->undefine( -script ) ;
$Macro->undefine( -variable ) ;
# list()
@macros = $Macro->list( -macro ) ;
@macros = $Macro->list( -macro, -namesonly ) ;
@scripts = $Macro->list( -script ) ;
@scripts = $Macro->list( -script, -namesonly ) ;
@variables = $Macro->list( -variable ) ;
@variables = $Macro->list( -variable, -namesonly ) ;
# load_file() - always treats the contents as within delimiters if we are
# doing embedded processing.
$Macro->load_file( $filename ) ;
# expand_file() - calls expand_embedded() if we are doing embedded
# processing otherwise calls expand().
$Macro->expand_file( $filename ) ;
@expanded = $Macro->expand_file( $filename ) ;
# expand()
$expanded = $Macro->expand( $unexpanded ) ;
$expanded = $Macro->expand( $unexpanded, $filename ) ;
# expand_embedded()
$expanded = $Macro->expand_embedded( $unexpanded ) ;
$expanded = $Macro->expand_embedded( $unexpanded, $filename ) ;
This bundle also includes the macro and macrodir scripts which allows us to expand macros without having to use/understand Text::MacroScript.pm, although you will have to learn the handful of macro commands available and which are documented here and in macro. macro provides more documentation on the embedded approach.
The macroutil.pl library supplied provides some functions which you may choose to use in HTML work for example.
<<lessSYNOPSIS
use Text::MacroScript ;
# new() for macro processing
my $Macro = Text::MacroScript->new ;
while( ) {
print $Macro->expand( $_ ) if $_ ;
}
# Canonical use (the filename improves error messages):
my $Macro = Text::MacroScript->new ;
while( ) {
print $Macro->expand( $_, $ARGV ) if $_ ;
}
# new() for embedded macro processing
my $Macro = Text::MacroScript->new( -embedded => 1 ) ;
# Delimiters default to
# or
my $Macro = Text::MacroScript->new( -opendelim => [[, -closedelim => ]] ) ;
while( ) {
print $Macro->expand_delimited( $_, $ARGV ) if $_ ;
}
# Create a macro object and create initial macros/scripts from the file(s)
# given:
my $Macro = Text::MacroScript->new(
-file => [ local.macro, ~/.macro/global.macro ]
) ;
# Create a macro object and create initial macros/scripts from the
# definition(s) given:
my $Macro = Text::MacroScript->new(
-macro => [
[ MAX_INT => 32767 ],
],
-script => [
[ DHM2S =>
[
my $s = (#0*24*60*60)+(#1*60*60)+(#2*60) ;
"#0 days, #1 hrs, #2 mins = $s secs"
],
],
-variable => [ *MARKER* => 0 ],
) ;
# We may of course use any combination of the options.
my $Macro = Text::MacroScript->new( -comment => 1 ) ; # Create the %%[] macro.
# define()
$Macro->define( -macro, $macroname, $macrobody ) ;
$Macro->define( -script, $scriptname, $scriptbody ) ;
$Macro->define( -variable, $variablename, $variablebody ) ;
# undefine()
$Macro->undefine( -macro, $macroname ) ;
$Macro->undefine( -script, $scriptname ) ;
$Macro->undefine( -variable, $variablename ) ;
# undefine_all()
$Macro->undefine( -macro ) ;
$Macro->undefine( -script ) ;
$Macro->undefine( -variable ) ;
# list()
@macros = $Macro->list( -macro ) ;
@macros = $Macro->list( -macro, -namesonly ) ;
@scripts = $Macro->list( -script ) ;
@scripts = $Macro->list( -script, -namesonly ) ;
@variables = $Macro->list( -variable ) ;
@variables = $Macro->list( -variable, -namesonly ) ;
# load_file() - always treats the contents as within delimiters if we are
# doing embedded processing.
$Macro->load_file( $filename ) ;
# expand_file() - calls expand_embedded() if we are doing embedded
# processing otherwise calls expand().
$Macro->expand_file( $filename ) ;
@expanded = $Macro->expand_file( $filename ) ;
# expand()
$expanded = $Macro->expand( $unexpanded ) ;
$expanded = $Macro->expand( $unexpanded, $filename ) ;
# expand_embedded()
$expanded = $Macro->expand_embedded( $unexpanded ) ;
$expanded = $Macro->expand_embedded( $unexpanded, $filename ) ;
This bundle also includes the macro and macrodir scripts which allows us to expand macros without having to use/understand Text::MacroScript.pm, although you will have to learn the handful of macro commands available and which are documented here and in macro. macro provides more documentation on the embedded approach.
The macroutil.pl library supplied provides some functions which you may choose to use in HTML work for example.
Download (0.036MB)
Added: 2007-05-31 License: Perl Artistic License Price:
876 downloads
Autoconf Macro Archive 2007-08-21 (cryp.to)
Autoconf Macro Archive aims to provide a collection of reusable Autoconf macros as free software. more>>
Autoconf Macro Archive aims to provide a collection of reusable Autoconf macros as free software.
The archive currently features more than 300 macros which perform portability tests ranging from compiler support for weird language extensions to automatic generation of sophisticated Automake rules.
However, all these macros have been contributed by friendly supporters of the cause from all over the Internet; the archive really just collects and distributes them.
<<lessThe archive currently features more than 300 macros which perform portability tests ranging from compiler support for weird language extensions to automatic generation of sophisticated Automake rules.
However, all these macros have been contributed by friendly supporters of the cause from all over the Internet; the archive really just collects and distributes them.
Download (0.53MB)
Added: 2007-08-03 License: GPL v3 Price:
812 downloads
AML Cartography 1.0
AML Cartography provides AML and C code and documentation for cartography. more>>
AML Cartography provides AML and C code and documentation for cartography within the ARC/INFO geographic information system.
The ARC Macro Language and C programs discussed in this guideline are available by anonymous ftp from sdcdg01.sdc.epa.gov and are in the files:
/pub/readme.cart
/pub/map_amls.tar.Z
/pub/map_design.tar.Z
/pub/map_post.Z
/pub/color_post.tar.Z
/pub/baw_post.tar.Z
<<lessThe ARC Macro Language and C programs discussed in this guideline are available by anonymous ftp from sdcdg01.sdc.epa.gov and are in the files:
/pub/readme.cart
/pub/map_amls.tar.Z
/pub/map_design.tar.Z
/pub/map_post.Z
/pub/color_post.tar.Z
/pub/baw_post.tar.Z
Download (MB)
Added: 2006-12-04 License: Public Domain Price:
1055 downloads
ChiliMac 0.1.0
ChiliMac is an interactive macro language implemented in 100% Java. more>>
ChiliMac is an interactive macro language implemented in 100% Java. It emphasizes ease of use and portability, while still providing several features for the power user.
It is built around XML (eXtensible Markup Language), which is a vibrant industry standard. This ensures compatibility with several third party tools and remarkable flexibility.
ChiliMac processes source documents, performs the specified actions and then generates output from the processed source documents.
Installation:
ChiliMac currently lacks an automated installation procedure. This will be remedied in future versions. Until then, the following should serve as a guide to manual installation of ChiliMac.
Firstly, you must install a Java Standard Edition Runtime Environment 5.0 (1.5.0) or greater.
Next, you will need to download the ChiliMac binary (the JAR file) to a suitable location for your system. Finally, the tricky part, you have to manually integrate the ChiliMac binary into your system.
This varies greatly from system to system, but is generally achieved by creating a shell script or batch file and adding it to your systems path.
Alternatively, you can just run the ChiliMac binary from the command line as follows (where x.y.z is substituded with the actual version number of the JAR file):
java -jar chilimac-x.y.z-bin.jar
<<lessIt is built around XML (eXtensible Markup Language), which is a vibrant industry standard. This ensures compatibility with several third party tools and remarkable flexibility.
ChiliMac processes source documents, performs the specified actions and then generates output from the processed source documents.
Installation:
ChiliMac currently lacks an automated installation procedure. This will be remedied in future versions. Until then, the following should serve as a guide to manual installation of ChiliMac.
Firstly, you must install a Java Standard Edition Runtime Environment 5.0 (1.5.0) or greater.
Next, you will need to download the ChiliMac binary (the JAR file) to a suitable location for your system. Finally, the tricky part, you have to manually integrate the ChiliMac binary into your system.
This varies greatly from system to system, but is generally achieved by creating a shell script or batch file and adding it to your systems path.
Alternatively, you can just run the ChiliMac binary from the command line as follows (where x.y.z is substituded with the actual version number of the JAR file):
java -jar chilimac-x.y.z-bin.jar
Download (0.009MB)
Added: 2005-10-18 License: GPL (GNU General Public License) Price:
1466 downloads
cdp-tools
cdp-tools is a software that provides tools to work with the Cisco Discovery Protocol (CDP). more>>
cdp-tools is a software that provides tools to work with the Cisco Discovery Protocol (CDP).
They were written because of a particular hosting center that insisted on learning routes using CDP, and thusly required Cisco Switches for doing their dirty work.
cdp-listen/cdp-routemgr are proof-of-concepts that may be useful if you want to implement a similarly brain-damaged proposal.
cdp-send is a must-have tool if you are in that situation. It can pretend to be just about any kind of Cisco hardware you can imagine.
The source is a bit difficult to follow as a requirement was that it build under both the ancient libnet and the new libnet code. hence, much nasty macro-ing.
Enhancements:
- DESCRIPTION, README: More docs...
<<lessThey were written because of a particular hosting center that insisted on learning routes using CDP, and thusly required Cisco Switches for doing their dirty work.
cdp-listen/cdp-routemgr are proof-of-concepts that may be useful if you want to implement a similarly brain-damaged proposal.
cdp-send is a must-have tool if you are in that situation. It can pretend to be just about any kind of Cisco hardware you can imagine.
The source is a bit difficult to follow as a requirement was that it build under both the ancient libnet and the new libnet code. hence, much nasty macro-ing.
Enhancements:
- DESCRIPTION, README: More docs...
Download (0.016MB)
Added: 2005-11-11 License: GPL (GNU General Public License) Price:
1451 downloads
Helma 1.6.0
Helma is an open source web application framework. more>>
Helma is an open source web application framework for fast and efficient scripting and serving of your websites and Internet applications.
It is written in Java and employs Javascript for its server-side scripting environment, removing the need for compilation cycles and reducing development costs while giving you instant access to leverage the whole wealth of Java libraries out there.
Helma pioneered the simple and codeless mapping of application objects to database tables, which has only recently come into vogue with other web frameworks. In addition, an embedded object-oriented database performs automatic data persistence of unmapped objects.
Helma has proven itself to be stable and fast, capable of serving high traffic sites with hundreds of thousands of dynamic pages per day. The Austrian Broadcasting Corporation, popular weblog hosting sites such as antville.org, twoday.net, and blogger.de, among many others, have successfully been deploying Helma for several years.
Enhancements:
- This release adds subskins, macro pipes/filters, an update to Rhino 1.6, E4X support, the ability to define getters/setters, and many improvements to the host objects in the JavaScript environment.
<<lessIt is written in Java and employs Javascript for its server-side scripting environment, removing the need for compilation cycles and reducing development costs while giving you instant access to leverage the whole wealth of Java libraries out there.
Helma pioneered the simple and codeless mapping of application objects to database tables, which has only recently come into vogue with other web frameworks. In addition, an embedded object-oriented database performs automatic data persistence of unmapped objects.
Helma has proven itself to be stable and fast, capable of serving high traffic sites with hundreds of thousands of dynamic pages per day. The Austrian Broadcasting Corporation, popular weblog hosting sites such as antville.org, twoday.net, and blogger.de, among many others, have successfully been deploying Helma for several years.
Enhancements:
- This release adds subskins, macro pipes/filters, an update to Rhino 1.6, E4X support, the ability to define getters/setters, and many improvements to the host objects in the JavaScript environment.
Download (4.2MB)
Added: 2007-07-20 License: BSD License Price:
826 downloads
Exact Build
Exact Build project is a sane GNU Auto replacement. more>>
Exact Build project is a sane GNU Auto replacement. For portable build systems nowadays normally GNU autoconf and the associated companiens such as automake and libtool. However albeit portable they are rather crufty to use. The various macro expansion and generation steps extremely blow up the initial definitions and make execution slow and debugging a nightmare.
Even with the enourmous code bloat, it does not have a wide feature set and neither allows to maximize the gain of parallel builds nor other state-of-the-art compiler features. Manual tinkering is needed in such cases.
Mostly due the code bloat but also to obtain features such as mximal parallel build and object output seperated cleanly from the source, we create our own set of Makefiles for the non-recursive build system and shell scripts for configuration, if required by the software module (some straight forware code does come without a configure script at all).
<<lessEven with the enourmous code bloat, it does not have a wide feature set and neither allows to maximize the gain of parallel builds nor other state-of-the-art compiler features. Manual tinkering is needed in such cases.
Mostly due the code bloat but also to obtain features such as mximal parallel build and object output seperated cleanly from the source, we create our own set of Makefiles for the non-recursive build system and shell scripts for configuration, if required by the software module (some straight forware code does come without a configure script at all).
Download (MB)
Added: 2006-05-10 License: GPL (GNU General Public License) Price:
1268 downloads
Condor 6.8.5
Condor schedules and runs remote CPU intensive applications using the idle cycles of distributively owned workstations. more>>
Condor schedules and runs remote CPU intensive applications using the idle cycles of distributively owned workstations.
It monitors a pool of machines to find idle machines that are then used to complete submitted jobs, and also provides checkpointing and remote system mechanisms that allow for job migration and transparent remote execution.
Enhancements:
- Ports to x86 Debian 4.0, Mac OS X 10.3, and Mac OS X 10.4 have been added.
- A configuration macro COLLECTOR_REQUIREMENTS has been added to filter out unwanted ClassAd updates.
- There are numerous bugfixes.
<<lessIt monitors a pool of machines to find idle machines that are then used to complete submitted jobs, and also provides checkpointing and remote system mechanisms that allow for job migration and transparent remote execution.
Enhancements:
- Ports to x86 Debian 4.0, Mac OS X 10.3, and Mac OS X 10.4 have been added.
- A configuration macro COLLECTOR_REQUIREMENTS has been added to filter out unwanted ClassAd updates.
- There are numerous bugfixes.
Download (MB)
Added: 2007-06-02 License: BSD License Price:
882 downloads
Parrot::OpTrans 0.4.5
Parrot::OpTrans is a Perl module that can transform Ops to C Code. more>>
Parrot::OpTrans is a Perl module that can transform Ops to C Code.
Parrot::OpTrans is the abstract superclass for the Parrot op to C transforms. Each transform contains various bits of information needed to generate the C code, and creates a different type of run loop. The methods defined here supply various default values and behaviour common to all transforms.
The subclass hierarchy is as follows:
OpTrans
|_________________________
| | |
C CGoto Compiled
| |
CPrederef |
| | |
| |_________|
| |
CSwitch CGP
Class Methods
new()
Returns a new instance.
Instance Methods
prefix()
Returns the default Parrot_ prefix.
Used by Parrot::Ops func_name() to individuate op function names.
suffix()
Implemented in subclasses to return a suffix with which to individuate variable names. This default implementation returns an empty string.
defines()
Implemented in subclasses to return the C #define macros required.
opsarraytype()
Returns the type for the array of opcodes. By default here its an array opcode_t, but the prederef runops core uses an array of void* to do its clever tricks.
core_type()
Implemented in subclasses to return the type of core created by the transform. This default implementation raises an exception indicating that the core type is missing. See the Parrot_Run_core_t enum in include/parrot/interpreter.h for a list of the core types.
core_prefix()
Implemented in subclasses to return a short prefix indicating the core type used to individuate core function names.
run_core_func_decl($base)
Optionally implemented in subclasses to return the C code for the run core function declaration. $base is the name of the main ops file minus the .ops extension.
ops_addr_decl($base_suffix)
Optionally implemented in subclasses to return the C code for the ops address declaration. $base_suffix is the name of the main ops file minus the .ops extension with suffix() and an underscore appended.
run_core_func_decl($base)
Optionally implemented in subclasses to return the C code for the run core function declaration. $base is the same as for run_core_func_decl().
run_core_func_start()
Implemented in subclasses, if run_core_func_decl() is implemented, to return the C code prior to the run core function.
run_core_after_addr_table($base_suffix)
Optionally implemented in subclasses to return the run core C code for section after the address table. $base_suffix is the same as for ops_addr_decl().
run_core_finish($base)
Implemented in subclasses to return the C code following the run core function. $base is the same as for run_core_func_decl().
init_func_init1($base)
Optionally implemented in subclasses to return the C code for the cores init function. $base is the same as for run_core_func_decl().
init_set_dispatch($base_suffix)
Optionally implemented in subclasses to return the C code for initializing the dispatch mechanism within the cores init function. $base_suffix is the same as for ops_addr_decl().
Macro Substitutions
The following methods are called by Parrot::OpFile to perform ops file macro substitutions.
access_arg($type, $value, $op)
Implemented in subclasses to return the C code for the specified op argument type and value. $op is an instance of Parrot::Op.
gen_goto($where)
The various goto_X methods below call this method with the return value of an expr_X method (implemented in subclass).
restart_address($address)
Implemented in subclasses to return the C code for restart ADDRESS($address).
restart_offset($offset)
Implemented in subclasses to return the C code for restart OFFSET($offset).
goto_address($address)
Transforms the goto ADDRESS($address) macro in an ops file into the relevant C code.
goto_offset($offset)
Transforms the goto OFFSET($offset) macro in an ops file into the relevant C code.
goto_pop()
Transforms the goto POP($address) macro in an ops file into the relevant C code.
expr_offset($offset)
Implemented in subclasses to return the C code for OFFSET($offset). Called by goto_offset().
expr_address($address)
Implemented in subclasses to return the C code for ADDRESS($address). Called by goto_address().
<<lessParrot::OpTrans is the abstract superclass for the Parrot op to C transforms. Each transform contains various bits of information needed to generate the C code, and creates a different type of run loop. The methods defined here supply various default values and behaviour common to all transforms.
The subclass hierarchy is as follows:
OpTrans
|_________________________
| | |
C CGoto Compiled
| |
CPrederef |
| | |
| |_________|
| |
CSwitch CGP
Class Methods
new()
Returns a new instance.
Instance Methods
prefix()
Returns the default Parrot_ prefix.
Used by Parrot::Ops func_name() to individuate op function names.
suffix()
Implemented in subclasses to return a suffix with which to individuate variable names. This default implementation returns an empty string.
defines()
Implemented in subclasses to return the C #define macros required.
opsarraytype()
Returns the type for the array of opcodes. By default here its an array opcode_t, but the prederef runops core uses an array of void* to do its clever tricks.
core_type()
Implemented in subclasses to return the type of core created by the transform. This default implementation raises an exception indicating that the core type is missing. See the Parrot_Run_core_t enum in include/parrot/interpreter.h for a list of the core types.
core_prefix()
Implemented in subclasses to return a short prefix indicating the core type used to individuate core function names.
run_core_func_decl($base)
Optionally implemented in subclasses to return the C code for the run core function declaration. $base is the name of the main ops file minus the .ops extension.
ops_addr_decl($base_suffix)
Optionally implemented in subclasses to return the C code for the ops address declaration. $base_suffix is the name of the main ops file minus the .ops extension with suffix() and an underscore appended.
run_core_func_decl($base)
Optionally implemented in subclasses to return the C code for the run core function declaration. $base is the same as for run_core_func_decl().
run_core_func_start()
Implemented in subclasses, if run_core_func_decl() is implemented, to return the C code prior to the run core function.
run_core_after_addr_table($base_suffix)
Optionally implemented in subclasses to return the run core C code for section after the address table. $base_suffix is the same as for ops_addr_decl().
run_core_finish($base)
Implemented in subclasses to return the C code following the run core function. $base is the same as for run_core_func_decl().
init_func_init1($base)
Optionally implemented in subclasses to return the C code for the cores init function. $base is the same as for run_core_func_decl().
init_set_dispatch($base_suffix)
Optionally implemented in subclasses to return the C code for initializing the dispatch mechanism within the cores init function. $base_suffix is the same as for ops_addr_decl().
Macro Substitutions
The following methods are called by Parrot::OpFile to perform ops file macro substitutions.
access_arg($type, $value, $op)
Implemented in subclasses to return the C code for the specified op argument type and value. $op is an instance of Parrot::Op.
gen_goto($where)
The various goto_X methods below call this method with the return value of an expr_X method (implemented in subclass).
restart_address($address)
Implemented in subclasses to return the C code for restart ADDRESS($address).
restart_offset($offset)
Implemented in subclasses to return the C code for restart OFFSET($offset).
goto_address($address)
Transforms the goto ADDRESS($address) macro in an ops file into the relevant C code.
goto_offset($offset)
Transforms the goto OFFSET($offset) macro in an ops file into the relevant C code.
goto_pop()
Transforms the goto POP($address) macro in an ops file into the relevant C code.
expr_offset($offset)
Implemented in subclasses to return the C code for OFFSET($offset). Called by goto_offset().
expr_address($address)
Implemented in subclasses to return the C code for ADDRESS($address). Called by goto_address().
Download (3.1MB)
Added: 2006-07-06 License: Perl Artistic License Price:
1205 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 macro 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