World: r3wp

I am completely happy with the way load works in this regard. A given 
date string must comply with the rebol syntax and have valid sub-values 
otherwise I don't want it. If messy data is coming in, just catch 
errors loading it from a string. Simple.

Petr, 29-Feb-2006 is always an invalid date. You can't say "Under 
some condition it could be even valid date (leap year)" because the 
year 2006 is specified in that date, and 2006 is not a leap year.


Data types have syntactic forms and semantic constraints. In order 
for the loader to recognize the data type, the syntactic form must 
be followed. In order for the resulting data to be valid, the semantic 
constraints must be obeyed. One such constraint is that date! values 
must correspond to a date on the calendar. Semantic violations are 
the bugs that all of that nasty exploit code does its job.

Sorry, "code uses to do its job."

Well, I checked with my paper-based calendar, and it isn't able to 
hancle 2006-02-29 either.So it may be OK that way ;-)

load-relaxed: func [string /local res sp parseblk] [
    sp: charset " ^/^-"
    parseblk: func [blk string /local val] [
        parse string [
            some [

                #"[" string: (string: parseblk val: make block! 16 string append/only 
                blk val) :string
                |

                #"(" string: (string: parseblk val: make paren! 16 string append/only 
                blk val) :string
                |

                #"]" string: (either block? blk [return string] [append blk "]"])
                |

                #")" string: (either paren? blk [return string] [append blk ")"])
                |

                string: skip (either error? try [set [val string] load/next string] 
                [

                    append blk copy/part string string: any [find string sp tail string]
                ] [
                    append blk :val
                ]) :string
            ]
        ]
        string
    ]
    parseblk res: make block! 16 string
    res
]

>> load-relaxed {10-Feb-2006 20-Feb-2006 29-Feb-2006 1-Mar-2006}
== [10-Feb-2006 20-Feb-2006 "29-Feb-2006" 1-Mar-2006]

>> load-relaxed {10-Feb-2006 20-Feb-2006 [29-Feb-2006 1-Mar-2006]}
== [10-Feb-2006 20-Feb-2006 ["29-Feb-2006" 1-Mar-2006]]

(just to give an idea)

thanks :-)

so... what are you going to do with "29-Feb-2006" ?

hmm, why send/attach sends jpeg in some non standard way? When I 
normally receive jpeg, first it is related to jpeg icon, second it 
is displayed in my email directly ....

ah, the difference is:

Content-Type: image/jpeg; name="2.jpg"
Content-Transfer-Encoding: base64
Content-Disposition: inline; filename="2.jpg"

--__REBOL--View--1.3.2.3.1--5318724__
Content-Type: application/octet-stream; name="bay.jpg"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="bay.jpg"

rebol does not recognise filetype .... so it uses application/octec-stream 
.... too many gotchas here, maybe it would be better to construct 
complete headers. Will look into some alternative attachment sending 
scripts on rebol.org ....

Rebol doesn't have a jpeg datatype, so you would have to specify 
Content-Type to SEND.

Yes, look for another example which does this already.

thanks .... have you ever heard of this cid: protocol thingy?

source send
source build-attach-body
source make-mime-header
;now to find that..

ah, build-attach-body ... did not know there are other functions 
involved ...

however, I can't parametrise 'send further, so ....

but you can check for suffix maybe

I can adapt thouse functions probably though ... I need to make different 
headers .... build-attach-body uses application/octect-stream, without 
ability to parametrise for e.g.

How come you are sending JPEGs ? I thought you would want to keep 
open the possibility of creating your postcard images using rebol, 
therefore it's better to get PNG working, isn't it ?

not sure .... but it could be so ....

simply the plan is - get jpeg (source file), compose with text, send 
inline, not even as an attachement. It is just that I did not heard 
about cid: container email reference before ... do all mailers handle 
pngs?

I am also not sure, how many ppl has turned off ability to display 
html content in email .... maybe it would be better to actually not 
send post-card .... but post a link to on-server stored image?

I will play with what was requested (sending an image) and I will 
see how can I handle it ...

There is also something like an inline-image inside the tag.

<img src="data:image/png;base64,iVBORw0KGgo..." alt="Testbild" />
but non-ie

'make-mime-header is inside 'build-attach-body.

make-mime-header: func [file] [
        net-utils/export context [

            Content-Type: join {application/octet-stream; name="} [file {"}]
            Content-Transfer-Encoding: "base64"

            Content-Disposition: join {attachment; filename="} [file {"
}]
        ]
    ]

i guess if you patch there based on "suffix? file" it should work

Maybe this useful to someone


delimit: func [data /quoted /with separator  [string! char!]  /local 
result quote][

    result: copy {}

    unless with [separator: ","]

    quote: either quoted [:mold][func[x][x]]
    append result quote form first data

    foreach value next data [
      append result separator
      append result quote form value

    ]

]



delimit [1 2 3] ;== "1,2,3"

delimit/with [1 2 3] ":" ;== "1:2:3"

delimit/quoted [1 2 3] ;== {"1","2","3"}

delimit/quoted/with [1 2 3] "|" ;== {"1"|"2"|"3"}

insert insert tail result separator quote form value

keep in mind that mold uses {} instead of "" in a number of cases 
(included when the size of the string is greater than a certain amount)

I have to encrypt some rather large files .. many megabytes.  Is 
there an encryption port that will do this in Rebol?  Or does encryption 
require that the whole file be in memory?

I don't think encryption changes the file-length, so you could just 
choose a large chunk size and encrypt those separately.

it does.

http://www.rebol.com/docs/encryption.html#section-3.1"It is possible 
to copy from the port before all data has been written"

any reason why Rebol has a get-env function, but not the set-env?

http://www.rebol.com/docs/view1300.html

run 	Runs the system application associated with a file.
 	
I'm sure that is not working ...

http://www.rebol.org/cgi-bin/cgiwrap/rebol/ml-display-thread.r?m=rmlPRTS
on how to set the environment variables in win32

using the win32 api

hmm.  Doesn't work.

Graham, there are two good reasons for that: Security and portability. 
Some platforms have one environment, some have per-process, some 
have global and per-user (like Windows) - which environment do you 
want to set? As for security, if you set any variable other than 
per-process it can affect the behavior of other programs, an ability 
that should be restricted in a sandboxed environment.


You should check out command line apps that you can call to set the 
various environments on your platform. If the REBOL process doesn't 
have call because of security restrictions, it shouldn't be able 
to set environment variables anyways.

run is available in ios. Somewhere i read in windows one can type 
a filename in shell, like text.txt, and windows launches the accosiated 
application. If that works, maybe with 'call too?

I think the lack of 'run in other than IOS is some type of oversight.

I agree

I wonder why using the windows 32 api, I still can't set the user 
environment variables

In linux they are copied for each process, not shared AFAIK. MAybe 
windows does the same?

; Does this work for you Graham?

REBOL []

; GET-ENV is a standard REBOL function now

; environment variable APIs
; msvcrt.dll
; getenv _putenv _environ
; char *getenv( const char *varname );
; int _putenv( const char *envstring );

lib:  load/library %msvcrt.dll

get-env: make routine! [
	varname [string!]
	return: [string!]
] lib "getenv"

put-env: make routine! [
	env-string [string!]
	return:    [integer!]
] lib "_putenv"

remove-env-var: func [name [string!]] [put-env join name "="]

env-var-exists?: func [name [string!]] [
	either "^@" = get-env name [false][true]
]

tz-set: make routine! [
	return:    [integer!]
] lib "_tzset"

print get-env "path"
print get-env "lib"
print get-env "temp"
print get-env "test"

if 0 <> put-env "test=blah" [
	print "error writing environment variable"
]
print get-env "test"
remove-env-var "test"
print mold get-env "test"

print get-env "TZ"
tz-set

free lib

halt