-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
thanks to all of those who provided some information on an ooRexx
grammar. Here, I want to share a central finding and my conclusion from it.
Parsing (oo)Rexx is hard. The reason for this is that a symbol can be a
symbol or a keyword, dependin
Well, you could try writing more test cases for the different
categories as I get them done. You also might want to start writing
tests for the parser class that uses regex patterns of the type I've
already got working. We're definitely at a point where things can be
done in parallel.
Rick
On S
Original Message
Subject: Re: [Oorexx-devel] Regular Expressions "first light" achieved!
Date: Sun, 25 Apr 2010 16:24:08 -0400
From: Gil Barmwater
To: Open Object Rexx Developer Mailing List
References:
YEAH! I've done an update and see you've added a bunch of stuff so I
nee
On Sun, Apr 25, 2010 at 2:06 PM, David Ashley
wrote:
> I need you to merge in the csvStream class into the Windows class. You
> should be able to copy what you are doing for rxftp except the the doc
> is rexextensions.pdf.
>
> I looked at it myself but I was not sure I covered all the bases.
Sur
yes, it's a minimalist distribution.
I can live with that, no problem.
Thanks !
Jean-Louis
--
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourc
Reading a little bit about Puppy Linux, it sounds like it is a very
stripped down Linux distribution. So perhaps they went a little too
far in removing things.
Bruce
On Apr 25, 2010, at 2:11 PM, David Ashley wrote:
Not ever having dealt with Puppy Linux I am really surprised. All
modern L
Not ever having dealt with Puppy Linux I am really surprised. All modern
Linux file systems support extended attributes since a late version of
the 2.4 kernel. That was over 5 years ago. Even the Mac supports
extended attributes.
They are all available in ext2, ext3, ext4, RiserFS, btrfs, and
Mark -
I need you to merge in the csvStream class into the Windows class. You
should be able to copy what you are doing for rxftp except the the doc
is rexextensions.pdf.
I looked at it myself but I was not sure I covered all the bases.
Thanks,
David Ashley
---
Hi
I can't compile rexxutil.cpp under PuppyLinux because xattr/xattr.h is not
found.
Maybe I need to install something, I did not investigate.
Temporarily bypassed by surrounding with
#if defined( HAVE_ATTR_XATTR_H)
I don't mind to stay like that, I have just to be careful to not commit that
in tr
YEAH! I've done an update and see you've added a bunch of stuff so I
need to have a more detailed look. I wasn't sure, for example, if you
were going to require the use of the Parser class to do matches but the
testGroup shows that you don't. Think I spotted a typo so a patch will
be forthco
I like this suggestion. And I think there's another category we'll
need to deal with for the regex extensions I'm working on. In this
extension, there's one set of classes that the typical user will deal
with, and there's an additional set of classes that only a person
wishing to enhance the comp
Mark,
You're correct. It turns out, I was reading the results incorrectly.
Line 66 was the line in the testgroup and the error was an assertion
failure. It just took me so long to get past that first assertion
that I assumed the 66 was in error :-)
Rick
On Sun, Apr 25, 2010 at 2:15 PM, Mark Mi
On Sun, Apr 25, 2010 at 11:11 AM, David Ashley
wrote:
> One more question, since this will set the standard. What about the
> docs? The doc for CSVStream is very small and could easily be merged
> into the rexxref doc. But is that the correct place for the doc? Should
> it be separate? I am mostly
Rick,
Looking a little closer, I think that I put in the
conditionObjectLineNumber() method as a fix to the line number problem
introduced after you traceback changes.
I only put in test trunk, not in the branches. In particular, the
4.0.1 branch does not have it.
I believe that:
https://oorex
One more question, since this will set the standard. What about the
docs? The doc for CSVStream is very small and could easily be merged
into the rexxref doc. But is that the correct place for the doc? Should
it be separate? I am mostly thinking about the future here. I cam
imagine extension cl
Yes, I agree. Its should go, somewhere, in the extensions directory.
--
Mark Miesfeld
On Sun, Apr 25, 2010 at 10:19 AM, Rick McGuire wrote:
> I'd just put it in extensions/CSVStream and then copy it to the build
> directory for the build. interpreter/RexxClasses should only contain
> class tha
On Sun, Apr 25, 2010 at 9:57 AM, Rick McGuire wrote:
> I suspect the changes I made to the tracebacks has messed up the
> failure reporting in the unit test framework. Everything is reporting
> the failure location as line 66. I'll try to take a look at this, but
> can you give me a pointer as
Ok, with my last commit, I've got a small bit of the regular
expression code working and the first set of passing test cases
checked in. Right now, the only expression type I've tested is the
simple string match filter (e.g. "foo"). This has tested a large
amount of the regex framework, now it's
I'd just put it in extensions/CSVStream and then copy it to the build
directory for the build. interpreter/RexxClasses should only contain
class that are part of the interpreter boot image (i.e, there's no
::requires necessary). All other classes are are extensions to the
base.
Rick
On Sun, Apr
All -
I was about to merge CSVStream into the trunk when I cam across
something. Where should I put it in the trunk tree? The class files I
have merged in the past were all dependent on rxsock so I put the into
the extensions/rxsock subdir. But when I went looking for examples of
other global
Mark,
I suspect the changes I made to the tracebacks has messed up the
failure reporting in the unit test framework. Everything is reporting
the failure location as line 66. I'll try to take a look at this, but
can you give me a pointer as to where I can find the code that handles
this?
Rick
-
21 matches
Mail list logo
