It installed without problems at home, and all my modules pass their
combined 2112 tests.
--
You received this message because you are subscribed to the Google Groups
"marpa parser" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Marpa allows you to discard parts of the input stream. And the tokens to be
discarded can have various forms. But you may well be better off matching
what you can be certain does appear. That means both defining exactly what
you want to find and somehow proving that what's in the part you wish
Hi
You did not specify a preferred language, but if you're comfortable with
Perl, see GraphViz2::Marpa on my Marpa
homepage: http://savage.net.au/Marpa.html. In particular, the method
_validate_event() shows how to handle the case of 2 lexeme-driven events
triggered at the same time.
The
Hi Daniel
Have you seen the unofficial Marpa home
page: http://savage.net.au/Marpa.html?
--
You received this message because you are subscribed to the Google Groups
"marpa parser" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Sigh. That should read 'main' module not 'mail' module.
--
You received this message because you are subscribed to the Google Groups
"marpa parser" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to marpa-parser+unsubscr...@googlegroups.com.
For more
Kind words indeed.
--
You received this message because you are subscribed to the Google Groups
"marpa parser" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to marpa-parser+unsubscr...@googlegroups.com.
For more options, visit
Glad to help. But as for the uninteresting parts, my fear is that you'll
need to more-or-less define them just to be able to tell Marpa what to
skip. I wonder if using priorities would be best, so telling Marpa the
interesting parts have high priority and the other part have low priority
>
> Hmmm. Bit hard to argue with that. But then, I'm so I like Bob Dylan..
>
That should read: Hmmm. Bit hard to argue with that. But then, I'm so
/old/ I like Bob Dylan..
--
You received this message because you are subscribed to the Google Groups
"marpa parser" group.
To
Hmmm. Bit hard to argue with that. But then, I'm so I like Bob Dylan..
--
You received this message because you are subscribed to the Google Groups
"marpa parser" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Poetry it might be, but beautiful it ain't!
--
You received this message because you are subscribed to the Google Groups
"marpa parser" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to marpa-parser+unsubscr...@googlegroups.com.
For more options, visit
Using this material, I've added 2 new questions to the
FAQ: http://savage.net.au/Perl-modules/html/marpa.faq/faq.html. Nos 144 and
145.
--
You received this message because you are subscribed to the Google Groups
"marpa parser" group.
To unsubscribe from this group and stop receiving emails
(1) On-the-fly fiddling of the grammar is in - ta-da! - the FAQ:
http://savage.net.au/Perl-modules/html/marpa.faq/faq.html#q126
(2) Tutorials and articles are on Marpa's unofficial home
page: http://savage.net.au/Marpa.html#Tutorials
--
You received this message because you are subscribed to
I have a vague idea that several years ago (5 or so?) someone else was
trying to parse VHDL using Marpa. Quite possibly it was discussed on
google+ or our irc channel. Perhaps re-google?
--
You received this message because you are subscribed to the Google Groups
"marpa parser" group.
To
Check your LICENSE files - FSF has a new physical address:
Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
--
You received this message because you are subscribed to the Google Groups
"marpa parser" group.
To unsubscribe from
http://phys.org/news/2014-06-ambiguous-words-easier.html#nRlv
--
You received this message because you are subscribed to the Google Groups
"marpa parser" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to marpa-parser+unsubscr...@googlegroups.com.
For
There is already a Marpa-based parser for
SQL: https://github.com/jddurand/MarpaX-Languages-SQL2003-AST
--
You received this message because you are subscribed to the Google Groups
"marpa parser" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Also, on Marpa's home page (http://savage.net.au/Marpa.html#Perl_Packages)
you'll find various modules which use that pre-lexeme event mechanism.
These are just mine; there may be others:
o GraphViz2::Marpa
o MarpaX::Demo::StringParser (used to investigate issues before
incorporation into the
My first though is make it work and then optimize it (if that's possible).
Classic anti-premature-optimization-101!
--
You received this message because you are subscribed to the Google Groups
"marpa parser" group.
To unsubscribe from this group and stop receiving emails from it, send an email
http://savage.net.au/Ron/html/Understanding.Marpa-style.action.subs.parameters.html
--
You received this message because you are subscribed to the Google Groups
"marpa parser" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
spacebat has replied.
--
You received this message because you are subscribed to the Google Groups
"marpa parser" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to marpa-parser+unsubscr...@googlegroups.com.
For more options, visit
MarpaX::Demo::SamplesScripts
(https://metacpan.org/pod/MarpaX::Demo::SampleScripts) ships with
scripts/heredoc.pl, which parses heredocs.
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails
I'm delighted to see latk has investigated this thoroughly, and we have a
fix.
I had problems with this 2 or 3 years ago, and documented it in
http://savage.net.au/Perl-modules/html/marpa.papers/chapter3.html. Search
that page for Moo.
--
You received this message because you are subscribed
On Monday, 9 March 2015 11:21:23 UTC+11, Jeffrey Kegler wrote:
It's nice to be compared with those making real contributions to
progress. I believe, though, that all real progress comes from a source
larger than an individual, and belongs to that source, more than to the
individual. Of
Marpa::R2 V 2.104. Test statistics:
Fails: 0. Files: 40. Modules: 9. Passes: 9. Tests: 418. Total: 392.
Duration: 54 seconds
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send
In the past, for MarpaX::Languages::SVG::Parser, I
used MarpaX::Grammar::GraphViz2 (yes, it's not listed in the pre-reqs) to
generate the demo output.
This in turn used MarpaX::Grammar::Parser which used Marpa to generate a
tree of the grammar, and MarpaX::Grammar::Parser restructured that
Progess! MarpaX::Languages::SVG::Parser now works, since I replaced
XML::SAX::ParserFactory with XML::Parser. I still need to re-write part of
the docs.
The problem remains that to generate the demo page I need Dump::TreeDumper,
which won't install because it needs Devel::Size, which is broken
Type: It's important to be able to be able in para 10.
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
to marpa-parser+unsubscr...@googlegroups.com.
For more
$work is chewing up time, which is good, so I've decided to press ahead
with testing Marpa, but to ignore the 3 modules of mine which have problems
under Perl 5.20.2:
Marpa::R2 V 2.103009. Test statistics:
Fails: 0. Files: 38. Modules: 8. Passes: 8. Tests: 364. Total: 338.
Duration: 38
A scary article on algorithmic
patenting:
http://yro-beta.slashdot.org/story/15/02/17/2032207/algorithmic-patenting
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
I should add to rns' compliment that I do not use code which promotes
ambiguity. In all the cases I've dealt with so far, I've been able to avoid
it without that interfering with the quality of the software.
I either pre-empt ambiguity by crafting the grammar in such a way as to
stop it, or I
I think this strategy would be completely infeasible for a real grammar.
Perhaps you meant that for the grammar you have to contend with, but I
still disagree. There are 2 courses of action here too (which is always
better than having 1 or none):
1: Extend the original grammar so Marpa
On Tuesday, 10 February 2015 14:24:56 UTC+11, Thomas Weigert wrote:
Thanks, Ron.
I see how the Ruby Slippers can work if you know ahead of time what the
text will be that we need to insert into the input, so we can secret it
away before calling read. I guess I could get this to work by
$many x $thanx;
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
to marpa-parser+unsubscr...@googlegroups.com.
For more options, visit
Outputs tables in any one of several supported types.
Features:
o Generic interface to all supported table formatso Separately specify
header/data/footer rowso Separately include/exclude header/data/footer rowso
Align cell values
Each column has its own alignment option, left, center or
Dave - Thanx for spelling out your ideas. I don't know where this
discussion will end up, but it's good to see the topic being debated.
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from
I had another read of the Log::Any docs, and it does look good. Just as
long as I never have to fight Log::Log4Perl.
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
Ah. It has an adapter for Log::Handler. Let me think about it.
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
to marpa-parser+unsubscr...@googlegroups.com.
For more
One reason is that I wanted the modules to be a light-weight as possible. I
always use Log::Handler myself, but I'll look at MooX::Role::Logger.
Actually, I'm not sure I've ever heard of it.
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To
No - I do not know of any. Of course, the most sophisticated approach would
be to write a Marpa grammar which replicated that module's grammar, and
then we could more-or-less automatically convert all
Parse::RecDescent-based module into Marpa based ones ;-). I would not
expect such conversion
I've released V 1.06.
The most noticeable change is that parse() now takes a hash, whose keys can
be any of length, pos, options or text.
Also, the constant 'debug' is now called 'print_debugs'.
Lastly, errors are no longer printed by default. You can turn on the new
constant 'print_errors'
I've also blogged about it (but you comment here
too):
http://blogs.perl.org/users/ron_savage/2015/01/a-note-about-x500dn-and-x500dnmarpa.html
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving
(1)
I like having an event interface to discarding, but for people using the
action style, how to they access discards?
(2)
[During event processing]: Without a pause clause, how I do retrieve the
text discarded?
--
You received this message because you are subscribed to the Google Groups
Excellent. Thanx!
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
to marpa-parser+unsubscr...@googlegroups.com.
For more options, visit
Marpa::R2 V 2.102. Test statistics:
Fails: 0. Files: 27. Modules: 9. Passes: 9. Tests: 358. Total: 358.
Duration: 54 seconds
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send
I've released V 1.03:
1.03 2015-01-06T08:57:35
- No code changes.
- Expand the explanation in the FAQ as to why you can't call escape_char(),
open() or close()
after calling new().
- Add xt/author/changes.t.
- Reformat datestamps in this file, so I can use Test::CPAN::Changes in
And he's my article on this
module: http://savage.net.au/Ron/html/Fancy.Matching.of.Delimited.Text.html
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
This module parses the template strings used in Perl's pack() and unpack()
functions.
The results of the parse are stored in a Tree managed by
https://metacpan.org/release/Tree.
This is really an exercise in my personal grammar study and development,
rather than being part of any great plan.
V 1.02 has been released. Recent changes:
1.02 Wed Dec 31 11:10:00 2014
- Change the default value for text() from '' to \''. That was a typo fix.
- Add the length() and pos() mutators, to allow the user to control the
call to the recognizer's
read() method. See the FAQ.
- Add the
There are 2 ways to handle this:
o Pre-process the input, so 'select top 5' becomes 'select'.
o Change the grammar.
If choosing the 2nd, I'd subclass MarpaX::Languages::SQL2003::AST and
commit myself to adding as much MS-specific code to the grammar as needed
to make the project work. The
I meant to add that I've moved completely away from actions to events, and
that's how I think when I approach such problems.
Some people may not want to do that, of course. And it may not be
compatible with the super class anyway.
--
You received this message because you are subscribed to the
To expand: The distro ships with scripts/synopsis.pl. So, that app allows
end users to run the code without ever having to look at the grammar, i.e.
the grammar is invisible.
The module can then be seen as a wrapper around something 'which just
works'. We know it's the grammar, but casual
V 1.01 has been released. See the Changes file for details.
And I've suggested on the dbi-mailing list that perhaps this module could
be used for the proposed new '?' escaping mechanism. We'll see.
--
You received this message because you are subscribed to the Google Groups
marpa parser
Text::Balanced::Marpa V 1.00 is now on CPAN.
I'm hoping this module will entice many more people to embrace the Marpa
way of doing things.
It's not on MetaCPAN yet, but you can read the docs
http://savage.net.au/Perl-modules/html/Text/Balanced/Marpa.html already.
--
You received this message
I was indirectly referring to Jeffrey's comment a few months ago about my
Marpa.html, were he indicated he'd let me choose text precisely because
it's on my web site.
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this
Overall, I think Marpa should be presented as mature, modern, and immensely
powerful.
The web site should be aimed at beginners, with clear indications as to
where experts
can go for more details.
Any examples should be complete, use modern Perl constructs, and have error
checking.
I'm not
GraphViz2::Marpa has been updated to V 2.03. The extra features are used by
the just-released GraphViz2::Marpa::PathUtils V 2.00.
The demo page for the former
is http://savage.net.au/Perl-modules/html/graphviz2.marpa/index.html.
And the demo page for the latter
is
Could anybody comment about the below specific question and direct me to
the correct place where to get the information
The object contains these:
sample#1
bless( [
[
0,
6,
'CREATE'
],
[
7,
6,
Hi Zeev
Have you seen this: http://troels.arvin.dk/db/rdbms/
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
to marpa-parser+unsubscr...@googlegroups.com.
For more
I should have added: I saw that link in the docs for SQL::Dialect.
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
to marpa-parser+unsubscr...@googlegroups.com.
For
Thanx - in various ways.
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
to marpa-parser+unsubscr...@googlegroups.com.
For more options, visit
This is a big day for me. This release is the last of my modules in which
I've worked to replace Marpa::XS with Marpa::R2.
I've left the previous release - V 1.13 - on CPAN because
GraphViz2::Marpa::PathUtils depends on it. The latter now needs to be
re-written.
--
You received this message
OK
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
to marpa-parser+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Marpa does it out of box. Exactly.
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
to marpa-parser+unsubscr...@googlegroups.com.
For more options, visit
A quite useable parser based on the Marpa algorithm is available...
You've taken understatement to a ridiculous level! I would have said
something like: An effective and efficient parser implementing these ideas,
which is already very successful, is available
Also, I'd remove 1 word: we
https://en.wikipedia.org/wiki/OPML
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
to marpa-parser+unsubscr...@googlegroups.com.
For more options, visit
Say I want a program to provide an option for a user to abort the run if an
ambiguous grammar is detected.
Should I test the return of just 1 of the above methods in preference to
the other? If so, which?
I'm also thinking of whether it makes sense to report something to the user
after
Enlightenment!
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
to marpa-parser+unsubscr...@googlegroups.com.
For more options, visit
Yep, might as well bite the bullet.
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
to marpa-parser+unsubscr...@googlegroups.com.
For more options, visit
Did you have a specific web page in mind?
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
to marpa-parser+unsubscr...@googlegroups.com.
For more options, visit
Marpa is so amazing that just about any claim it makes can be hard to
believe until you've tried it yourself.
Sour grapes is different. That's when superficial responses are all of the
form: Yes, but it doesn't have an interface in language $X.
--
You received this message because you are
Too true.
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
to marpa-parser+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
MarpaX::Grammar::Parser gets Marpa to parse a grammar (using Jeffrey's
code) and outputs a tree managed by Tree::DAG_Node.
That tree is compressed and passed to MarpaX::Grammar::GraphViz2, for
rendering as SVG.
The compression mainly results from discarding info Marpa stores regarding
offsets
Thanx. I've fixed that.
And I've added a para just above the heading 'An Intermediate Summary
http://savage.net.au/Ron/html/Conditional.preservation.of.whitespace.html#___top'
about Marpa not using lookahead. I'd appreciate another pair of eyes in
that area.
--
You received this message
Done!
http://savage.net.au/Ron/html/Conditional.preservation.of.whitespace.html
It's good to get this out of the way, since at $work there's been a minor
disaster (not of my making) which, next week, I'll probably have to handle
by switching from part-time to full-time for 2 months. We'll see.
That's Marpa's own grammar, so libmarpa reads that and uses it (that file)
to validate it (that file), which is indeed self-referential.
Then Marpa uses that grammar to validate your grammar.
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To
I googled for DASH language, and it seems no-one else was silly enough to
call their language that, so I've decreed that the grammar included in this
module to be for DASH language.
Since the grammar and parser handles a range of string types, all having
their embedded spaces protected, it may
Actually, it's the integration of POD with code which will make it hard to
replace, unlike developing something (Markdown, anyone?) to run in
parallel, which is much easier, and which has been done many times already.
--
You received this message because you are subscribed to the Google Groups
One of the comments to the swim proposal pointed to http://commonmark.org/.
I've just added it to the list of parser
proposals: http://savage.net.au/Perl-modules/html/marpa.papers/chapter5.html.
We can joke: That's the good thing about standards, there are so many to
choose from. (Nods
Yes, this is a problem, but they've definitely got the right idea trying to
pin down the grammar.
Presumably the lack of a BNF-format grammar reflects their lack of
understanding that Marpa can help.
Did you submit feedback? If not, let us know and I'll at least ask them to
consider BNF (to
https://medium.com/@prufrock123/js-dot-notation-vs-bracket-notation-797c4e34f01d
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Graph::Easy::Marpa only ever parsed a fraction of the language supported by
Graph::Easy, and it was never my intention to support all that language
anyway.
The exact language parsed by MarpaX::Demo::StringParser is being
documented, and a renderer for it, using calls to GraphViz2, has been
Following on from the above...
The point of the new work is to make the parsing code more robust and
remove a bug I found.
It also gives me the opportunity to more formally define the language
parsed, without reference to the docs for
Graph::Easy::Marpa.
Further, the new code will be extended
For your delectation:
http://savage.net.au/Ron/html/The.Prehistory.of.Marpa.html
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Marpa::R2 V 2.096. Test statistics:
Fails: 0. Files: 296. Modules: 6. Passes: 6. Tests: 296.
Duration: 43 seconds
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
Here's a potential project:
https://publicsuffix.org/
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
to marpa-parser+unsubscr...@googlegroups.com.
For more
Yes, Marpa seems like overkill. But it'd be slightly interesting to handle
the between-lines linkages.
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Ok, ok! Case closed :-).
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
to marpa-parser+unsubscr...@googlegroups.com.
For more options, visit
Presumably that means call series_restart() after ambiguous() but before
value(), right :-)?
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
I'll cut down the big program. I can see how to call the same code twice,
with the same input but a different value for a new parameter which
exercises the calls in question.
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from
I've switched over to gists because they allow comments:
https://gist.github.com/ronsavage/a372ca2802f47808374b
As for desired behaviour, you'll note cases 0 4 print Output: !-! OK
count: 2. This means the parse is correct, which is true. So why don't all
cases do that?
I accept there could
Is ambiguity always a fatal error?
I realize the libmarpa does not force that, but are you saying the user
should automatically assume that's the case?
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop
Thanx.
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
to marpa-parser+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On Wednesday, 1 October 2014 15:17:34 UTC+10, Jeffrey Kegler wrote:
OK. Ambiguity is a property of the parse (grammar + input). Typically
you'll only check for it once the input is complete. So checking inside
the read()/resume() loop is not something you'll typically do, because the
Sounds good, and I for one deeply appreciate putting quality above new
features when it comes to priorities.
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
An update on MarpaX::Demo::SampleGrammars. I've haven't started it yet, but
after huge progress on the original problem over the last couple of days, I
may well do it on Sunday.
I have at least 5 demos ready.
I'll create dirs (in the distro) such as data/nested.strings/,
data/quoted.strings/,
Not at first. Consider:
V 1 or 2: :include file_name = /my/grammars/quoted.strings.bnf
V 1 or 2: :include file_name = /my/grammars/quoted.strings.bnf namespace
= xyz
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this
Sounds good. Of course, the namespace declaration could be inside the
include file.
--
You received this message because you are subscribed to the Google Groups
marpa parser group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
I've had a play with your (very fancy) code, but I'm now working purely on
an extension of the grammar this thread started with.
And the more I play with Marpa the more astonished I am by its power.
--
You received this message because you are subscribed to the Google Groups
marpa parser
I've developed a grammar (with help from various people of course) for
quoted strings: http://scsys.co.uk:8002/424926
Requirements:
o Strings must be quoted
o Strings are either single or double quoted
o The escape character is \
o If the string is single quoted, internal single quotes must
Thanx for the link.
I did not consider that case, since I'm really interested in the Graphviz
DOT file format, where quotes if any must be double quotes, and internal
quotes must be escaped.
However, I will examine the code you link to, since ever such example is
interesting.
--
You
1 - 100 of 183 matches
Mail list logo
