Free Merchant Account Setup

2003-10-01 Thread patrica


  
  

  
  

  


   
   


   
  



   
  
		  10% OFF Purchase with Coupon Code: 0620CMLimited time offer.

  


   
  


   
   
  A Virtual Terminal
allows your business to process credit cards through any computer
with an internet connection. No longer is there any need for
a bulky box with an extra phone line to process your credit
card transactions. 

It's easy!  Simply follow these steps:



  
Open
  your favorite web browser.
  
  
Login
  to your online account.
  
  
Enter
  or swipe the credit card and transaction amount.
  
  
Click
  the "process" button to accept payments!
  



  A Virtual Terminal can be deployed and activated at any location
  within seconds, and there is no software to install. You have
  24/7 access to real-time accounting, batch control, account
  settings, and credit card processing. 
  
  Click here
  to be removed. 
  


   
   


   
  


   
  

  Cheaper
and saves you money.
  Free
merchant account with purchase.
  Reduction
of credit card processing fees. 
  Elimination
of outdated physical credit card terminals. 
  Elimination
of the dedicated phone lines for the terminals. 
  Instant
upgrades without investment in new hardware. 
  Rapid
deployment and scalability of processing capabilities. 
  Faster
transaction processing. 




   
   


   
  


   
  

  Access
to an easy interface for processing transactions. 
  Swiped
or manual credit card transactions. 
  Secure
transactions from anywhere in the world. 
  Web
based real-time accounting of transactions. 
  Recurring
transactions for subscriptions or memberships. 
  Fraud
protection via (AVS) and (CVV2) settings. 
  Stores
customer profiles for repeat customers. 
  Instant
functional updates. 
  No
software to install. 
  E-commerce
and wireless credit card terminal monitoring. 



  


  



   



  



  



  



  



  



  



  



  

		






CLASSPATH separator in Makefile.am

2003-10-01 Thread David Neary

Hi,

I'm not quite sure whose job this is (automake or autoconf - I suspect the
latter), so I'm sending this to both lists. Hope this doesn't upset anyone
:)

I have a java project which, among other things, recuperates the CLASSPATH
environment variable, and adds some stuff to it in the Makefile. I have a
Makefile.am target which looks like this...

gnu/%.class: @srcdir@/src/gnu/%.java
@JAVAC@ @JAVACFLAGS@ \
-d . \
-classpath "${CLASSPATH}:@srcdir@/src:." \
@srcdir@/src/gnu/xml/libxmlj/transform/*.java

This is fine on Unix, but obviously doesn't go down well on Win32. Modifying
the :s to ;s explicitly in the Makefile.am gets it through the Windows
build, which is fine. But is there a way to have an AC_SEPARATOR defined
which "converts" stuff like this to the correct format for the target
platform at the configure stage? It would be nice not to have to manually
edit makefiles and configure scripts in Win32.

Also, one other thing which is definitely autoconf related...

The macros AC_CHECK_CLASS_COMPILATION and AC_CHECK_CLASS use the same
CLASSPATH convention (: separator), causing them to break on Win32. The fix
seems to be to manually edit the generated configure script to get it
working right.

And one last (automake related) thing - for inner classes (classes called
Parent$Inner or somesuch), how can one escape the $ from the Makefile.am
through the Makefile.in to the Makefile itself? I seem to have the \$ in the
Makefile.am replaced by $ in Makefile.in, and then $Inner is replaced by ""
in the filan Makefile, resulting in just Parent. Do I need to have \$ in
the Makefile.am?

Cheers,
Dave.

--
David Neary
Phenix Engineering
110 ave Jean Jaures, 69007 Lyon 




Verba Volant 02-OCT-2003

2003-10-01 Thread Verba Volant

Verba Volant 02-OCT-2003,
Every day a new quotation translated into many languages. 

_ 
Quotation of the day: 
Author -
Edward
Dahlberg
English - a strong foe is better
than a weak friend
Albanian -
më mirë një armik i betuar se sa një
mik çka
Aragones -
un enemigo zereño ye millor que un
amigo feble
Asturian -
un enemigu fuerte ye meyor qu'un
amigu floxu
Basque -
arerio amorratua, segur aski,
adiskide epela baino hobe da
Bolognese -
un nemîg tamóggn l é méi d un amîg
fiâp
Brazilian Portuguese -
um inimigo acirrado é melhor do que
um amigo fraco
Breton -
un enebour kreñv zo gwell eget ur
c'heneil flav
Calabrese -
'nu nemico tuostu è megliu di
'n'amico accussì accussì
Catalan -
un enemic acèrrim és millor que no un
amic dèbil
Croatian -
jak neprijatelj bolji je od slaboga
prijatelja
Danish -
en stærk fjende er bedre end en svag
ven
Dutch -
een sterke vijand is beter dan een
zwakke vriend
Esperanto -
forta malamiko estas pli bona ol
malforta amiko
Estonian -
tugev vaenlane on parem kui nõrk
sõber
Finnish -
hyvä vihollinen on parempi kuin huono
ystävä
Flemish -
een sterke vijand is beter dan een
zwakke vriend
French -
un ennemi fort est mieux qu'un ami
inconsistent
Galician -
un inimigo forte é mellor ca un amigo
frouxo
German -
ein starker Feind ist besser als ein
energieloser Freund
Griko Salentino -
nan anemìco poddhin àscimo è ccàddio
azze na ffilo ìu ce ìu
Hungarian -
az erõs ellenség mindig jobb, mint
egy gyenge barát
Italian -
un nemico acerrimo è sicuramente
preferibile a un amico così così
Judeo Spanish -
un enemigo inatchi es mijor ke un
amigo tivio
Latin -
acerrimus hostis melior est quam
amicus infirmus
Leonese -
un enemigu curiosu ye meyor qu'un
amigu sonce
Lombardo -
on nemis fòrt l'è pussee mèj d'on
amis mòll
Mudnés -
l'è mî un amîgh impestê piotôst che
ùn a mèza vìa
Papiamentu -
un enemigu fuerte ta mihó ku un amigu
débil
Parmigiano -
al nemigh pú cativ l'é semper meij
che un amigh a mez
Piemontese -
un enmis fòrt a l'é mej che un amis
fiap
Polish -
lepiej zawziety nieprzyjaciel niz
lichy przyjaciel
Portuguese -
um inimigo forte é melhor que um
amigo fraco
Romagnolo -
un amigh sa e maroun l'è ad fatt mèi
d'un amigh adsé adsé
Roman -
un nemico tignoso é sicuramente mejo
de ´n´amico cosí cosí
Spanish -
un enemigo intenso es mejor que un
amigo descolorido
Swedish -
en stark fiende är bättre än en svag
vän
_

_
All languages, please click on this link: 
http://www.verba-volant.net/pls/vvolant/datecorps2.go_to?codice=938
_ 
To unsubscribe from Verba Volant, please follow this link:
http://www.verba-volant.net
alternatively write to the following address:
[EMAIL PROTECTED] always copying the EMAIL address written
after "X-RCPT-TO:"
<><>

hi automake ,see a dream team

2003-10-01 Thread barcelonasoccer
Title: The Barcelona soccer show






The Barcelona soccer show,  was
creat in 1997, in Copacabana beach, was a homage to Ronaldinho, player of
espanish team in epoch. In begin was only a good team, winner of the various
championship. But because  the
absence of suport and publicity of this sport in Brasil, I did creat in 2000, a
“show-team” of  the Barcelona,
taking alon the players more  beauty
and feminine to change the image of the  woman
soccer , showing that the woman can play soccer and no lost the feminine way.
The result of this idea was very good with diverse reportages in TV and
newspaper. Because very success that had our team in Brasil, becoming a big
atraction to the public, I believe, that my team will have same success in
others place of the world. This way I did send this email to help me try close
apresentation in your country. This apresentation can be free ( with all
expenses paid: transport, alimentation and hotel ) or with a reward in case of
apresentation with gol of gain.


I wait a answer.


Thanks


 
PS:
See below, someones reportages of our team



Alexandre Saleh


Responsable of the Barcelona Soccer Show


(
02121 24807366 )



 

 










Re: precompiled header suggestion

2003-10-01 Thread Tom Tromey
> "Rob" == Robert Collins <[EMAIL PROTECTED]> writes:

>> Recently gcc added precompiled header support.  This is mostly useful
>> for C++, but C might benefit in some cases too.

Rob> Are you planning on doing this, or just sketching the design and hoping
Rob> for volunteer contributions?

I'm hoping someone else will do it :-)


Rob> What might be a useful starting point is some manual test cases or
Rob> sample rules, to aim for.

No problem.  libstdc++ is already using it.  I've appended some
snippets from their Makefile.am.

We could probably already get most of this by abusing _PROGRAMS.
That's ugly though.

I've also appended the section of the gcc manual explaining
precompiled headers.

Tom


pch_input = ${host_builddir}/stdc++.h
pch_output_builddir = ${host_builddir}/stdc++.h.gch
pch_source = ${glibcxx_srcdir}/include/stdc++.h
PCHFLAGS=-Winvalid-pch -Wno-deprecated -x c++-header $(CXXFLAGS)
if GLIBCXX_BUILD_PCH
pch_build = ${pch_input}
pch_install = install-pch
else
pch_build =
pch_install =
endif

# Build a precompiled C++ include, stdc++.h.gch.
${pch_input}: ${allstamped} ${host_builddir}/c++config.h ${pch_source}
touch ${pch_input}; \
if [ ! -d "${pch_output_builddir}" ]; then \
  mkdir -p ${pch_output_builddir}; \
fi; \
$(CXX) $(PCHFLAGS) $(AM_CPPFLAGS) ${pch_source} -O0 -g -o 
${pch_output_builddir}/O0g; \
$(CXX) $(PCHFLAGS) $(AM_CPPFLAGS) ${pch_source} -O2 -g -o 
${pch_output_builddir}/O2g;



@node Precompiled Headers
@section Using Precompiled Headers
@cindex precompiled headers
@cindex speed of compilation

Often large projects have many header files that are included in every
source file.  The time the compiler takes to process these header files
over and over again can account for nearly all of the time required to
build the project.  To make builds faster, GCC allows users to
`precompile' a header file; then, if builds can use the precompiled
header file they will be much faster.

To create a precompiled header file, simply compile it as you would any
other file, if necessary using the @option{-x} option to make the driver
treat it as a C or C++ header file.  You will probably want to use a
tool like @command{make} to keep the precompiled header up-to-date when
the headers it contains change.

A precompiled header file will be searched for when @code{#include} is
seen in the compilation.  As it searches for the included file
(@pxref{Search Path,,Search Path,cpp.info,The C Preprocessor}) the
compiler looks for a precompiled header in each directory just before it
looks for the include file in that directory.  The name searched for is
the name specified in the @code{#include} with @samp{.gch} appended.  If
the precompiled header file can't be used, it is ignored.

For instance, if you have @code{#include "all.h"}, and you have
@file{all.h.gch} in the same directory as @file{all.h}, then the
precompiled header file will be used if possible, and the original
header will be used otherwise.

Alternatively, you might decide to put the precompiled header file in a
directory and use @option{-I} to ensure that directory is searched
before (or instead of) the directory containing the original header.
Then, if you want to check that the precompiled header file is always
used, you can put a file of the same name as the original header in this
directory containing an @code{#error} command.

This also works with @option{-include}.  So yet another way to use
precompiled headers, good for projects not designed with precompiled
header files in mind, is to simply take most of the header files used by
a project, include them from another header file, precompile that header
file, and @option{-include} the precompiled header.  If the header files
have guards against multiple inclusion, they will be skipped because
they've already been included (in the precompiled header).

If you need to precompile the same header file for different
languages, targets, or compiler options, you can instead make a
@emph{directory} named like @file{all.h.gch}, and put each precompiled
header in the directory.  (It doesn't matter what you call the files
in the directory, every precompiled header in the directory will be
considered.)  The first precompiled header encountered in the
directory that is valid for this compilation will be used; they're
searched in no particular order.

There are many other possibilities, limited only by your imagination,
good sense, and the constraints of your build system.

A precompiled header file can be used only when these conditions apply:

@itemize
@item
Only one precompiled header can be used in a particular compilation.
@item
A precompiled header can't be used once the first C token is seen.  You
can have preprocessor directives before a precompiled header; you can
even include a precompiled header from inside another header, so long as
there are no C tokens before the @code{#include}.
@item
The precompiled header file must be produced for t

Re: CLASSPATH separator in Makefile.am

2003-10-01 Thread Nic Ferrier
David Neary <[EMAIL PROTECTED]> writes:

> Hi,
> 
> I'm not quite sure whose job this is (automake or autoconf - I suspect the
> latter), so I'm sending this to both lists. Hope this doesn't upset anyone
> :)
> 
> I have a java project which, among other things, recuperates the CLASSPATH
> environment variable, and adds some stuff to it in the Makefile. I have a
> Makefile.am target which looks like this...
> 
> gnu/%.class: @srcdir@/src/gnu/%.java
> @JAVAC@ @JAVACFLAGS@ \
> -d . \
> -classpath "${CLASSPATH}:@srcdir@/src:." \
> @srcdir@/src/gnu/xml/libxmlj/transform/*.java
> 
> This is fine on Unix, but obviously doesn't go down well on Win32. Modifying
> the :s to ;s explicitly in the Makefile.am gets it through the Windows
> build, which is fine. But is there a way to have an AC_SEPARATOR defined
> which "converts" stuff like this to the correct format for the target
> platform at the configure stage? It would be nice not to have to manually
> edit makefiles and configure scripts in Win32.

I think the Makefile.am author simply has to use a variable to
specify the separator.

The variable can easily be OS dependant. The fact that it doesn't do
it in this project is an ommission.


Nic Ferrier





How one could integrate Automake in an IDE ?

2003-10-01 Thread Alain Magloire

Bonjour

First, I'm not subscribe to the list ... please CC, thanks.

Question:
I'm curious on how the autoXXX tools like automake etc .. can
be integrated nicely part of an IDE.  So far what I've seen
is not suitable enough ...
If you know of a good integration, please send the URL.

I'm looking at the Multipage Editor design, when one tab control(page)
shows the raw source and the  others shows a different "view" of the source
that can be edited by newbies easily, of course with round-trip(i.e. the raw
source Makefile.am reflects the other views vice-versa).

any comments.

Thanks.





Autoconf 2.57f is released

2003-10-01 Thread Akim Demaille

This is our candidate release for Autoconf 2.58.  We plan to release
it soon, so that Automake 1.8 can be released, hence Libtool 1.6, so
that GNU M4 2.0 can be shipped, enabling Autoconf 2.60 ;)

Please, test it thoroughly.

Akim, Alexandre, Jim, Paul, and Tom.


Here are the compressed sources:
  http://www.lrde.epita.fr/~akim/download/autoconf-2.57f.tar.gz   (1.2MB)
  http://www.lrde.epita.fr/~akim/download/autoconf-2.57f.tar.bz2  (837KB)

And here are xdelta-style diffs:
  http://www.lrde.epita.fr/~akim/download/autoconf-2.57d-2.57f.xdelta   (10KB)

Here are GPG detached signatures:
  http://www.lrde.epita.fr/~akim/download/autoconf-2.57f.tar.gz.asc
  http://www.lrde.epita.fr/~akim/download/autoconf-2.57f.tar.bz2.asc

Here are the MD5 and SHA1 signatures:

dd48fe8cf425f7068d729aa432df4527  autoconf-2.57f.tar.gz
385a923859a0e02e4c6f0ccc4f29b137  autoconf-2.57f.tar.bz2
4f342dbfbcee2648e7426c3f46f59fb8  autoconf-2.57d-2.57f.xdelta
9b1f3a2bfeb21e80813619e86cc5a52b7edaffbb  autoconf-2.57f.tar.gz
5dd5018ae395ed627384caf69460fea5006a037e  autoconf-2.57f.tar.bz2
2cda92c4f05799ace152744927152a1645030287  autoconf-2.57d-2.57f.xdelta

NEWS

* Major changes in Autoconf 2.57f

  Released 2003-10-01, by Akim Demaille.

* Major changes in Autoconf 2.57e

  Released 2003-09-29, by Akim Demaille.

** AC_CONFIG_COMMANDS
  The directory for its first argument is automatically created.  For
  instance, with

  AC_CONFIG_COMMANDS([src/modules.hh], [...])

  $top_builddir/src/ is created if needed.


ChangeLog entries:

**
ChangeLog
**
2003-10-01  Akim Demaille  <[EMAIL PROTECTED]>

Version 2.57f.

2003-09-30  Paul Eggert  <[EMAIL PROTECTED]>

* lib/Autom4te/XFile.pm: Use Errno.
(lock): Ignore ENOLCK errors.  Problem reported Andreas Schwab in
.

2003-09-30  Akim Demaille  <[EMAIL PROTECTED]>

* config/announce-gen (&print_news_deltas): Extracted from...
(&print_changelog_deltas): here.
(&news_file): Rename as...
(@news_file): this.

2003-09-30  Nicolas Joly  <[EMAIL PROTECTED]>

* lib/autoconf/fortran.m4 (_AC_PROG_FC): Remove files which might
have been created when invoking the compiler.
* tests/fortran.at (GNU Fortran 77): Quote $G77.

2003-09-29  Akim Demaille  <[EMAIL PROTECTED]>

Version 2.57e.

* config/mkinstalldirs: Upgrade.

2003-09-28  Paul Eggert  <[EMAIL PROTECTED]>

* lib/m4sugar/m4sh.m4 (AS_SHELL_SANITIZE): Set DUALCASE=1, for MKS sh.
Problem reported by Lars J. Aas in
.
(_AS_MKDIR_P_PREPARE): Change "rm -fr ./-p" to the more-conservative
"test -d ./-p && rmdir ./-p".  Suggested by Andreas Schwab in:
http://mail.gnu.org/archive/html/autoconf-patches/2003-09/msg00039.html

2003-09-26  Akim Demaille  <[EMAIL PROTECTED]>

* lib/autoconf/status.m4 (_AC_OUTPUT_COMMANDS): Make sure the
directory for AC_CONFIG_COMMANDS' first argument exists.
This makes valid the invocation of _AC_SRCPATH that follows.
Reported by Eric Sunshine.
* doc/autoconf.texi (Configuration Commands): Adjust.

2003-09-26  Akim Demaille  <[EMAIL PROTECTED]>

* bin/autoscan.in (Autom4te::FileUtils): Use it for find_file.
Reported by Ralf Corsepius.

2003-09-26  Akim Demaille  <[EMAIL PROTECTED]>

* lib/autoconf/general.m4 (AC_HELP_STRING): Don't overquote the
arguments.
Actually, use AU_ALIAS.
From Bruno Haible.

2003-09-26  Paul Eggert  <[EMAIL PROTECTED]>

* lib/m4sugar/m4sh.m4 (_AS_MKDIR_P_PREPARE): If mkdir -p . fails,
rm -fr ./-p to remove junk left behind on NextStep and OpenStep.
Problem reported by Eric Sunshine in:
http://mail.gnu.org/archive/html/autoconf-patches/2002-12/msg00014.html

2003-09-26  Akim Demaille  <[EMAIL PROTECTED]>

The test suite are sometimes assigning timings incorrectly.
Reported by Henk Krus.
Diagnosed by Nicolas Joly.

* lib/autotest/general.m4 (AT_CLEANUP): Rename AT_help as
AT_help_all.
Instead of making AT_help a sequence of assignments to grow
$at_help_all, just make AT_help_all be the growing contents of
$at_help_all, and make a single assignment in...
(AT_INIT): here.
(at_times_skip): Flip the meaning and rename as...
(at_times_p): this.
(AT_INIT): When summarizing the test that ran, remove
$at_times_file after use, and check it is present before trying to
use it.




Verba Volant 01-OCT-2003

2003-10-01 Thread Verba Volant

Verba Volant 01-OCT-2003,
Every day a new quotation translated into many languages. 

_ 
Quotation of the day: 
Author -
Carlo
Emilio Gadda
Italian - non tutti sono
condannati ad essere intelligenti
Albanian -
jo të gjithë janë të dënuar të jenë
inteligjentë
Aragones -
no toz son condenatos a estar
intelixéns
Asturian -
nun toos tán condergaos a ser
intelixentes
Basque -
guztiak ere ez daude adimentsuak
izatera kondenaturik
Bolognese -
brîSa tótt i én cundanè a avair dal
capéss
Bresciano -
mja togg j'è cundanagg a eser
enteligenti
Breton -
n'eo ket an holl a gondaoner da vezañ
speredek
Calabrese -
nun tutti su cundannati ad essi
'ntelliggenti
Catalan -
no tots estan condemnats a ser
intel·ligents
Croatian -
nije svatko proklet pamecu
Danish -
ikke alle er dømt til at være
intelligente
Dutch -
niet iedereen is ertoe veroordeeld,
intelligent te zijn
English -
not everyone is condemned to being
intelligent
Esperanto -
ne cxiuj estas kondamnitaj esti
inteligentaj
Estonian -
mitte kõiki pole süüdistatud
intelligentsuses
Finnish -
kaikkia ei ole tuomittu olemaan
älykkäitä
Flemish -
niet iedereen is gedoemd intelligent
te zijn
French -
tout le monde n'est pas condamné à
être intelligent
Furlan -
no son ducj condanats a jessi
inteligjents
Galician -
non todos están condenados a ser
intelixentes
German -
nicht alle sind dazu verdammt,
intelligent zu sein
Griko Salentino -
en ine oli cundannài na noìsune
Hungarian -
nem mindenki van megverve azzal, hogy
intelligens
Judeo Spanish -
no estamos todos kondenados a ser
intelidjentes
Latin -
non omnes damnantur
intelligentia
Leonese -
nun tamos toos condergaos a ser
intelixentes
Limburgian -
alleman ès nie mèt slimmighèts
aongemok
Lombardo -
minga tucc hinn costrengiuu a vess
intelligent
Mudnés -
an gh'avàm mènga l'ôblig per lêz
d'êser inteligèint
Papiamentu -
no tur hende ta kondená pa ta
inteligente
Parmigiano -
miga tutti j en condané a esr
inteligent
Piemontese -
pa tuit a son condanà à esse
inteligent
Polish -
nie wszyscy sa skazani na bycie
inteligentnymi
Portuguese -
nem todos estão condenados a ser
inteligentes
Romagnolo -
menga ciaschedoun l'è cumdamné ma
esser intilizìnt
Roman -
mica so´ tutti condannati a esse´
inteligenti
Sicilian -
non tutti sunnu cunnannati a iessiri
intelligenti
Spanish -
no todos están condenados a ser
inteligentes
Swedish -
inte alla är dömda att vara
intelligenta
Zeneize -
miga tutti son condannæ à ëse
intelligenti
_

_
All languages, please click on this link: 
http://www.verba-volant.net/pls/vvolant/datecorps2.go_to?codice=937
_ 
To unsubscribe from Verba Volant, please follow this link:
http://www.verba-volant.net
alternatively write to the following address:
[EMAIL PROTECTED] always copying the EMAIL address written
after "X-RCPT-TO:"
<><>