On Fri, Jan 27, 2006 at 05:53:06PM -0800, Sean Machin wrote:
parse2.c from the example code. It failed with an error:
camera_test.xml:65: validity error : Content model of rule is not
determinist: ((input | (input , (operator , input)+)) , output+)
/rule
I'm using version
Sergey Scobich wrote:
I have a proposal to add VS.2005 project files to CVS in order to easy
compilation for Win32 users.
Personally I would like to see the win build be contained using the
current build system and think any compatibility issues building with
2005 should be addressed there.
Hello Rob,
Current command line build works perfectly only after a went through the
stage were you need to set environment variables or put additional path's in
your system. It was not as fast as I expected.
Idea is to provide to windows users more commonly used way of building the
product like
I agree, this would be a welcomed feature.
On 1/28/06, Sergey Scobich [EMAIL PROTECTED] wrote:
Hello Rob,
Current command line build works perfectly only after a went through the
stage were you need to set environment variables or put additional path's in
your system. It was not as fast as I
On Sat, Jan 28, 2006 at 02:26:07PM +0200, Sergey Scobich wrote:
Idea is to provide to windows users more commonly used way of building the
product like building the Visual Studio solution, were all environment
variables are already set.
Would you commit personally to ensure maintainance of
Hi Daniel,
I didn't see any problems in maintenance of these files so I'm ready to
maintain them for 3 years.
If you think that this will pollute CVS, or leave them unmaintainable - it's
ok, I understand.
It is always possible to reference to bugzilla link:
Liron wrote:
You're absolutely right about the don't fix it if it ain't broken
approach
but after reviewing the code I think that it's badly broken and I'll
explain:
It's true that those functions do different things but the common thing for
all of them is reading from a socket. As I
Hi all,
I'm having a rather strange problem, well... I'm having a global 'state'
variable that invokes (depending on certain input) other named templates
which then will invoke custom written XPath functions.
xsl:variable name='state'
...
xsl:call-template name='named-foo'/
...
