 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Darren New <dne### [at] san rrcom> wrote:
> outint'endian = little;
Exactly which language is this? And have you actually corroborated by
examining the resulting machine code that it indeed does as you say?
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Wed, 12 Mar 2008 09:15:42 +0000, Invisible wrote:
>>>> But if I wanted it to work all the time, I'd write it in C and be
>>>> done with it - then the shell doesn't come into play. :-)
>>> Yah, as I said, when it gets messy, I use Tcl. :-)
>>
>> Really the best option - remove the shell. :-)
>
> 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.
Jim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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
|
|
| |
| |
|
|
|
|
| |
