[DGD] explode bug?

[Felix A. Croes]

> during some work on getting heaven7 running on dgd 1.1 i ran into acurious
> thing.
>
> It seems like dgd's explode kfun won't expand a string like other drivers do
> if the first characters in the string are equal to the seperator used. It
> then skippes the first item.
>
> In my case (something like) :
>
> ~#~
> main
> ~#~
> hfsdgfh
> ~#~
>
> lost the main as first item i fthe seperator was "~#~\r\n" (and the file was
> saved as DOS file, ie with crlf . It worked ok if put a space in front of
> the string to be exploded.

I couldn't reproduce this.  Perhaps explode() is masked by a buggy efun in
the auto object?

There are no differences between explode() in 1.1 and in 1.1p4, by the way.


> Btw is it possible to fix the problem with macro/defines's & crlf's? It
> would be great if dgd would be able to accept both cr and crlf ended lines
> and would see an empty line as the end of a macro/defines (the multiline
> things with \ at the line ends). It would make editing under windows a lot
> easier.

It is certainly possible, but from my point of view it is not a problem,
which makes a "fix" undesirable.

Regards,
Dworkin