M0E Lnx wrote:
> I just tried that, and I get the same results. I dont know what the problem
> is..
>
> sCMD = "lzmadec " & chr(60) & space(1) & sFilePath
>
> for degbuggind, I print sCMD and all I get is "lzmadec". I can print
> sFilePath and I know for a fact is has a value.
>
How about this:
I just tried that, and I get the same results. I dont know what the problem is..
sCMD = "lzmadec " & chr(60) & space(1) & sFilePath
for degbuggind, I print sCMD and all I get is "lzmadec". I can print
sFilePath and I know for a fact is has a value.
On 7/23/08, Caveat <[EMAIL PROTECTED]> wrote:
>
Have you tried Chr$(60)?
Chr$(33) = ! Chr$(34) = " Chr$(35) = # Chr$(36) = $
Chr$(37) = % Chr$(38) = & Chr$(39) = ' Chr$(40) = (
Chr$(41) = ) Chr$(42) = * Chr$(43) = + Chr$(44) = ,
Chr$(45) = - Chr$(46) = . Chr$(47) = / Chr$(48) = 0
I'm writing an application that uses a shell like to perform some tasks.
I need to parse something like "lzmadec < " & sPath to the shell. The
problem is,
it seems that gambas is only parsing "lzmadec" and ignores everything
starting at the "<" to the end of the line.
I tried escaping the "<" li
Benoit Minisini schreef:
> On mercredi 23 juillet 2008, Ron wrote:
>
>> Hi,
>>
>> In my quest to parse a string to get some values from it, I ended up
>> with way to much string functions.
>>
>> So I want to parse it a bit more efficient with gb.pcre... so far so
>> good, but I 'm stumped as how
On mercredi 23 juillet 2008, Ron wrote:
> Hi,
>
> In my quest to parse a string to get some values from it, I ended up
> with way to much string functions.
>
> So I want to parse it a bit more efficient with gb.pcre... so far so
> good, but I 'm stumped as how to use it.
> Very sparse docs found on
Hi,
In my quest to parse a string to get some values from it, I ended up
with way to much string functions.
So I want to parse it a bit more efficient with gb.pcre... so far so
good, but I 'm stumped as how to use it.
Very sparse docs found on gambasdoc.org, but can anybody give an example?
L
