* Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 [2013-08-04 18:05]:
> There is already Regexp-Genex which portrays itself as a generator for
> regexes, but its functionality is different from your module, so it's
> a good idea to prevent confusion and avoid that overlap, "generator".
> To "generate" is about as useful as the
On Mon, 05 Aug 2013 11:45:52 -0500
Brian Katzung wrote:
> Good point. I read the OP's example and understood it to be
> case-insensitive, but even having seen it spelled out still didn't
> protect me from forgetting the detail (a "broken understanding")
> later. :-)
Having it spelled out is su
On 2013-08-05 10:58, David Cantrell wrote:
On Sun, Aug 04, 2013 at 03:28:23PM -0400, Shawn H Corey wrote:
On Sun, 04 Aug 2013 14:13:59 -0500
Brian Katzung wrote:
That's an interesting idea, but I'm not sure you're accomplishing
your stated goals. Consider that the RE /^\s*test\s*$/ is 14
chara
On Sun, Aug 04, 2013 at 03:28:23PM -0400, Shawn H Corey wrote:
> On Sun, 04 Aug 2013 14:13:59 -0500
> Brian Katzung wrote:
> > That's an interesting idea, but I'm not sure you're accomplishing
> > your stated goals. Consider that the RE /^\s*test\s*$/ is 14
> > characters and you've coded it in 91
On Sun, Aug 04, 2013 at 01:30:55PM -0400, Shawn H Corey wrote:
> On Sun, 4 Aug 2013 18:03:51 +0200
> Lars D? ? wrote:
> > This would be better in the Regexp top level namespace instead of
> > occupying its own:
> I chose the short name so it would be remembered. Long names
You originally said "easier to build and *understand*" (emphasis mine).
Machine code is not mnemonic, but assembly is. From where I sit, going
from APL to COBOL is a closer analogy. Speaking only for myself, I don't
see any "conceptual increment" (more power for less effort) in this
case. I ca
On Sun, 04 Aug 2013 14:13:59 -0500
Brian Katzung wrote:
> That's an interesting idea, but I'm not sure you're accomplishing
> your stated goals. Consider that the RE /^\s*test\s*$/ is 14
> characters and you've coded it in 91 non-white-space characters (650%
> of the original size).
The differen
On Sun, August 4, 2013 12:30 pm, Shawn H Corey wrote:
> On Sun, 4 Aug 2013 18:03:51 +0200
> Lars Dɪá´á´á´á´á´¡ 迪ææ¯ wrote:
>
>> This would be better in the Regexp top level namespace instead of
>> occupying its own:
>
> I chose the short name so it would be remembered. Long names aren't.
I have to agree with Lars. I would suggest that the long name is more
likely to found (people being more likely to scan the Regexp name space)
and the short name less.
- Brian
On 2013-08-04 12:30, Shawn H Corey wrote:
On Sun, 4 Aug 2013 18:03:51 +0200
Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 wrote:
This would be
On Sun, 4 Aug 2013 18:03:51 +0200
Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 wrote:
> This would be better in the Regexp top level namespace instead of
> occupying its own:
I chose the short name so it would be remembered. Long names aren't.
--
Don't stop where the ink does.
Shawn
This would be better in the Regexp top level namespace instead of
occupying its own:
cpan[1]> d //Regexp/
Database was generated on Sun, 04 Aug 2013 13:53:03 GMT
DistributionABIGAIL/Regexp-CharClasses-2009102801.tar.gz
DistributionABIGAIL/Regexp-Common-2013031301.tar.gz
I have started a Module I call REG (Regular Expression Generator) and
placed it in github (see below). The idea is to create REs by
called descriptive methods which generate the appropriate RE. For
example, to create a RE to match the word test in a string:
my $re_test = REG->string_begin()
12 matches
Mail list logo
