From Newsgroup: comp.sys.acorn.programmer

Can anyone remind me how you use the DDE_Utils commands from BASIC to
invoke a command-line program with a string of parameters that
potentially exceed 255 bytes in length (and thus give errors if
assembled into a BASIC string variable?)


So far as I can tell from inspection of what I was doing in !SideDiff
(which now crashes with a segmentation fault), you simply call DDEUtils_SetCLSize to point the OS to your buffer and then
DDEUtils_SetCL to run the command, but there seems to be some element missing...


DIM CLbuffer% 2600
SYS "DDEUtils_SetCLSize", 2600

$CLbuffer%="Show Wimp$Scrap"
SYS "DDEUtils_SetCL",CLbuffer%

does nothing, so far as I can see.
--
Harriet Bazley == Loyaulte me lie ==

Everyone hates me because I'm paranoid.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.sys.acorn.programmer

In message <4ab1e0e65a.harriet@bazleyfamily.co.uk>
Harriet Bazley <harriet@bazleyfamily.co.uk> wrote:

$CLbuffer%="Show Wimp$Scrap"
SYS "DDEUtils_SetCL",CLbuffer%

does nothing, so far as I can see.

Is CLbuffer% the same as CLbuffer$ at SYS or is there a difference with termination (0 and 13/10)?

Thomas Milius
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.sys.acorn.programmer

On 20 Sep 2023 as I do recall,
Thomas Milius wrote:

In message <4ab1e0e65a.harriet@bazleyfamily.co.uk>
Harriet Bazley <harriet@bazleyfamily.co.uk> wrote:

$CLbuffer%="Show Wimp$Scrap"
SYS "DDEUtils_SetCL",CLbuffer%

does nothing, so far as I can see.

Is CLbuffer% the same as CLbuffer$ at SYS or is there a difference with termination (0 and 13/10)?

The StrongHelp manual for "DDEUtils_SetCL" complains "The command line
is actually terminated at the first *control* character. This is very annoying" - but presumably use from BASIC is the reason why....
--
Harriet Bazley == Loyaulte me lie ==

ObChocolate: Nice!
--- Synchronet 3.21d-Linux NewsLink 1.2