To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.rcx.nqcOpen lugnet.robotics.rcx.nqc in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / RCX / NQC / 395
394  |  396
Subject: 
Re: NQC 2.1 b2 in beta test
Newsgroups: 
lugnet.robotics.rcx.nqc
Date: 
Mon, 17 Jan 2000 02:40:45 GMT
Viewed: 
1698 times
  
In article <3882382E.6F973085@munich.netsurf.de>, Uwe Denzer
<Uwe.Denzer@munich.netsurf.de> wrote:


I checked with the only compiler I have at home (Delphi), and it has no problem
with the format RcxCC is using, and it does no escaping at all. Tomorrow, I can
check with at least two other common Win32 devtools (Visual C++, VB) in the
office...


My test was a program like this:

#include <stdio.h>

int main(int argc, char**argv)
{
  int i;
  for(i=0; i<argc; ++i)
    printf("<%s>\n", argv[i]);
}


I built it under both Metrowerks and VC++.  Then I called the program with
various command lines to infer the escaping rules.  The two did not agree
on a few obscure cases, but both failed to parse the RcxCC exec line as
desired.  In short, both treat

"foo\" abc

As a single argument that looks like this:

foo" abc

And not two arguments

foo\
abc

The differences between the two mainly have to do with weird cases like \\\\"

Assuming that VC++ is the defacto standard here, I think RcxCC should at
least quote in a way that VC++ would handle correctly.  No escaping isn't
really an acceptable long-term solution, because even if I hack the
CodeWarrior libs to do this, people will still have problems if they use
VC++ to build NQC.

Dave Baum

--
reply to: dbaum at enteract dot com



Message has 1 Reply:
  Re: NQC 2.1 b2 in beta test
 
(I didn't have time today to check with VC++ and VB as I intended.) (...) Mhm, I see. This makes sense. The behavior of VC++ still strikes me as odd, but anyway if it's so, then your conclusion is obviously right, I'd say. Uwe (25 years ago, 17-Jan-00, to lugnet.robotics.rcx.nqc)

Message is in Reply To:
  Re: NQC 2.1 b2 in beta test
 
(...) Unfortunately, I don't know "official" rules nor did I find a place where to look them up. Nevertheless, I can only think that this whole escaping stuff is not compliant with normal, expected Win32 behavior. The backslash is the standard (...) (25 years ago, 16-Jan-00, to lugnet.robotics.rcx.nqc)

25 Messages in This Thread:







Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR