 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mike Raiford wrote:
> Nicolas Alvarez wrote:
>
>> And also one reason why command-line tools are better for many things.
>> (image editing probably not one of them)
>
> Funny, there's a set of commandline tools for just that called
> ImageMagick. :D
Image "editing"? Or simple image transformation operations?
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> Cool. I just hope your filenames don't contain any of the characters
>> that Tcl considers to be "special" either. :-P
>
> Well, I use C, and it deals with literal strings, but I suspect TCL is
> the same in that regard.
Tcl encodes all data types as strings. I've been bitten by this
before... You write a Tcl script, it works fine, and then it encounters
some input that happens to contain a curly-bracket or a dollar sign and
Weird Crap happens...
[I'm sure there's a way to avoid this. It's just tricky, and it makes me
nervous.]
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mike Raiford escribió:
> Nicolas Alvarez wrote:
>
>> And also one reason why command-line tools are better for many things.
>> (image editing probably not one of them)
>
> Funny, there's a set of commandline tools for just that called
> ImageMagick. :D
Well yeah. But you can't do as much as you can in photoshop.
Can you make a good-looking POV-Ray scene *without ever looking at the
result*? :)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Wed, 12 Mar 2008 19:02:00 +0000, Orchid XP v7 wrote:
>>> Cool. I just hope your filenames don't contain any of the characters
>>> that Tcl considers to be "special" either. :-P
>>
>> Well, I use C, and it deals with literal strings, but I suspect TCL is
>> the same in that regard.
>
> Tcl encodes all data types as strings. I've been bitten by this
> before... You write a Tcl script, it works fine, and then it encounters
> some input that happens to contain a curly-bracket or a dollar sign and
> Weird Crap happens...
That's one of the potential pitfalls with most scripting languages.
Jim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Eero Ahonen wrote:
> Well ok, after that you wrote about chopping the file, which practically
> is what split does, but it should be able to work without creating
> millions of (temp)files in the middle of the process.
The problem is the size of the file. If I split it after the fact, I now
have *two* files, the original and the new one. So now instead of half
an hour of deleting directory entries, I have three hours of copying
data, followed by five minutes of deleting one directory entry.
Split doesn't split a file. It writes new files, each of which contain
pieces of the previous file.
--
Darren New / San Diego, CA, USA (PST)
"That's pretty. Where's that?"
"It's the Age of Channelwood."
"We should go there on vacation some time."
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Invisible wrote:
> Cool. I just hope your filenames don't contain any of the characters
> that Tcl considers to be "special" either. :-P
I have, on occasion, got caught by a file whose name starts with ~. But
none of the other characters are special in Tcl file names. In
particular, spaces and brackets and such just don't come into play.
--
Darren New / San Diego, CA, USA (PST)
"That's pretty. Where's that?"
"It's the Age of Channelwood."
"We should go there on vacation some time."
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Orchid XP v7 wrote:
> Tcl encodes all data types as strings. I've been bitten by this
> before... You write a Tcl script, it works fine, and then it encounters
> some input that happens to contain a curly-bracket or a dollar sign and
> Weird Crap happens...
Only if you don't treat your lists as lists and your strings as strings.
Otherwise, the rules are extremely straightforward.
> [I'm sure there's a way to avoid this. It's just tricky, and it makes me
> nervous.]
I never get bitten by this. The only time this happens is when you pass
a string to something that indexes into a list, without first splitting
the string into lists appropriately.
--
Darren New / San Diego, CA, USA (PST)
"That's pretty. Where's that?"
"It's the Age of Channelwood."
"We should go there on vacation some time."
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp wrote:
> Darren New <dne### [at] san rrcom> wrote:
>> outint'endian = little;
>
> Exactly which language is this?
Ada. I am pretty sure it supports this.
> And have you actually corroborated by
> examining the resulting machine code that it indeed does as you say?
No. Never needed to. It's not the sort of thing you leave out of a
language you're programming flight control software in.
--
Darren New / San Diego, CA, USA (PST)
"That's pretty. Where's that?"
"It's the Age of Channelwood."
"We should go there on vacation some time."
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Darren New wrote:
> Warp wrote:
>> Darren New <dne### [at] sanrrcom> wrote:
>>> outint'endian = little;
>>
>> Exactly which language is this?
>
> Ada. I am pretty sure it supports this.
It turns out the syntax is
(The ' indicates a compile-time value, in much the same sense that
sizeof() is a compile-time function in C. Ada lets you read dozens of
these and set others, like the address, volitility, atomicity, etc.)
It also turns out it's not *quite* so straightforward especially for .
But clearly it's better to let the compiler do it in cases where it can
than to code different routines with #ifdef in there. Autoconf doesn't
make C portable - it rewrites your code to be non-portable to that
specific machine. :-)
--
Darren New / San Diego, CA, USA (PST)
"That's pretty. Where's that?"
"It's the Age of Channelwood."
"We should go there on vacation some time."
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> Tcl encodes all data types as strings. I've been bitten by this
>> before... You write a Tcl script, it works fine, and then it
>> encounters some input that happens to contain a curly-bracket or a
>> dollar sign and Weird Crap happens...
>
> Only if you don't treat your lists as lists and your strings as strings.
> Otherwise, the rules are extremely straightforward.
>
>> [I'm sure there's a way to avoid this. It's just tricky, and it makes
>> me nervous.]
>
> I never get bitten by this. The only time this happens is when you pass
> a string to something that indexes into a list, without first splitting
> the string into lists appropriately.
I'm pretty sure I remember several occasions where if a certain
expression happened to return only 1 item, it tried to interpret the
item as a list. IOW, when the expression finds multiple matches,
everything works fine, but when it finds exactly 1 match it malfunctions
horribly. Took me ages to figure out why...
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
