World: r3wp
[Core] Discuss core issues
older newer | first last |
GrahamC 12-Feb-2011 [955x6] | 8000 lines of IP ranges |
going to be a big file! | |
oops .. 3Mb file of ip addresses to block | |
the VID editor just died on that | |
222,000 lines of addresses | |
let's hope vbulletin doesn't choke | |
Andreas 12-Feb-2011 [961] | -> ~Chit Chat |
Brock 16-Feb-2011 [962x2] | Does anyone know why modifeid? and info? return a date without the time when accessing a file through ftp lon a windows ftp server? Is this a limitation of windows, the ftp scheme, the ftp server, or the version of Rebol (I'm using the latest 2.7 - activated ODBC connection all dll access)? Are there any known fixes to this - a quick google didn't find anything? |
ecall there is a ftp update out there, does anyone know if that fixes this limiation? | |
Maxim 16-Feb-2011 [964] | it should return the time, I've got ftp synching routines which use info? and use date/time. so I'd bet its a limitation on the server, or its using a non-standard date string in its LIST command. |
Brock 16-Feb-2011 [965] | Okay, I'll see if our server admin can change something that will help. Using Romano's FTP-Patch.r shows the date for files, but there is some code in place to get it to work from what I can tell. |
BrianH 16-Feb-2011 [966] | You might also try connecting with the FTP server with a command line client like NcFTP and looking at the listings directly. |
GrahamC 16-Feb-2011 [967x2] | or just modify the existing ftp client ... the formatting is a parse rule |
ftp protocol ... | |
BrianH 16-Feb-2011 [969] | I meant, look at the listings directly, so you know what to look for when modifying that parse rule :) |
Brock 16-Feb-2011 [970] | thanks for the input. I'll see what I can do. |
TomBon 22-Feb-2011 [971] | how to prevent binary data from spanning multiple lines? this #{ 3A 18 92 56 } should be this #{3A189256} is this possible? |
BrianH 22-Feb-2011 [972] | Afaik, binaries don't keep the info about how they were laid out on the page like blocks do. The whitespace won't be preserved when they are printed out. And there is no whitespace internally in the binary, just binary data. |
TomBon 22-Feb-2011 [973x2] | according to the above example I would like to store the binary via a tcp. any other possibility to transform the binary? while using enbase I have also todo a dehex after retrieving. would like to avoid this. |
the best would be if I could store just 3A189256 and then reform ist back to a binary. is this in general possible brian? | |
GrahamC 22-Feb-2011 [975] | tombon, the binary is not spanning mulitiple lines .. that's just a display issue? |
TomBon 22-Feb-2011 [976x4] | unforunatly not. when I compose the value pairs to transmit there occur a crlf within. so the key/value just store #{ |
for example: the store sequence is this {key^-1 value^-#{ 789CCBCA2E4EC9485348CC2ECE82D059C53960460E9005666465E74018C559D9 296919501A48A50000B5BE16913C000000 } | |
to lines separated by a tab for the key/value | |
is there any other compression which returns a string instead a binary? | |
GrahamC 22-Feb-2011 [980x3] | You can just form a binary ... to get a string |
Mind blank ..anyone got a routine to trim a particular character from the end of a string? I want to remove trailing pipe characters | |
I could reverse the string and then parse it using a charset .. but that seems crude ( any reason why the parse direction can not be made an option ? ) | |
BrianH 22-Feb-2011 [983x4] | That's one of the proposals that hasn't been implemented yet. |
Why not use FIND with the charset? | |
All trailing pipe characters? Do you want to remove any other characters other than | ? | |
>> b: charset [not "|"] == make bitset! [not bits #{00000000000000000000000000000008}] >> find/reverse/tail tail "abc|||" b == "|||" | |
GrahamC 22-Feb-2011 [987x2] | looks like R3 to me! |
I want to remove trailing | | |
BrianH 22-Feb-2011 [989] | For R2 you might need to complement the charset rather than using not. |
GrahamC 22-Feb-2011 [990] | I didn't know you could use find with a charset |
BrianH 22-Feb-2011 [991x2] | >> b: complement charset "|" == make bitset! #{ FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF } >> next find/reverse tail "abc|||" b == "|||" >> head clear next find/reverse tail "abc|||" b == "abc" |
FIND/reverse/tail doesn't work in R2. | |
GrahamC 22-Feb-2011 [993] | I'll give it a go... ta |
BrianH 22-Feb-2011 [994] | So you might need to do a bit of tweaking for the R2 version, but it's a start. |
GrahamC 22-Feb-2011 [995] | is this being backported to R2? |
BrianH 22-Feb-2011 [996] | FIND/reverse/tail works in R2, but not with charsets. It's a bug. |
GrahamC 22-Feb-2011 [997x2] | as I thought ... no find with charsets |
oh ... ooops | |
BrianH 22-Feb-2011 [999] | FIND works with charsets in R2, but the /tail option doesn't. It's a newly discovered (just now) bug. |
GrahamC 22-Feb-2011 [1000] | just now ?? |
BrianH 22-Feb-2011 [1001] | Yeah. By me, just now, while I was doing this experiment. |
GrahamC 22-Feb-2011 [1002] | neat |
BrianH 22-Feb-2011 [1003] | Thanks :) |
GrahamC 22-Feb-2011 [1004] | find/reverse tail a b only finds the first | |
older newer | first last |