![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Darren New wrote:
> http://harmful.cat-v.org/software/xml/s-exp_vs_XML
...what the HELL?
Is this guy has I point, I don't know what it is. I must have missed it
somewhere between the outbursts of delusional raving.
Seriously. XML is overcomplicated and so forth, and there are all mannar
of technical complaints you could make about it, but I see very little
technical material in this drivel.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 22-6-2009 4:50, Tim Attwood wrote:
>
> Personally I find flat tags clearer than forcing them into trees.
Am I the only one to read that as 'flat tax'?
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Patrick Elliott <sel### [at] npgcable com> wrote:
> Or.. It downloaded wrong (still does happen), got corrupted somehow,
> your application you wrote yourself isn't "writing" it out correctly, etc.
Named end tags are certainly not in any way the best way of dealing
with those problems.
--
- Warp
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Invisible wrote:
> Seriously. XML is overcomplicated and so forth, and there are all mannar
> of technical complaints you could make about it
http://www.w3.org/TR/xqueryx/#Examples
That's pretty special, right there...
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Warp wrote:
> Patrick Elliott <sel### [at] npgcable com> wrote:
>> Or.. It downloaded wrong (still does happen), got corrupted somehow,
>> your application you wrote yourself isn't "writing" it out correctly, etc.
>
> Named end tags are certainly not in any way the best way of dealing
> with those problems.
>
If you plan to have a machine look it over, true. Its "supposed" to be
sort of human readable though, and more conventional code type stuff,
especially if you are tired, can be damn hard to "see" mistakes in some
times. lol
--
void main () {
if version = "Vista" {
call slow_by_half();
call DRM_everything();
}
call functional_code();
}
else
call crash_windows();
}
<A HREF='http://www.daz3d.com/index.php?refid=16130551'>Get 3D Models,
3D Content, and 3D Software at DAZ3D!</A>
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |