OpenEuphoria

1. Re: Euphoria ctrl-c bug? [Reposted]

• Posted by Jason Gade <jaygade at yahoo.com> Feb 12, 2006
• 1954 views

Robert Craig wrote:
> 
> Jason Gade wrote:
> > Is this normal operation for the interpreter? The interpreter does not stop
> > executing Euphoria code when ctrl-c is pressed but instead takes over the
> > input
> > buffer and continues to execute loops like this?
> 
> I'm not sure if check_break/allow_break works reliably with
> all the C compilers I'm using, on all platforms. I'll look into
> it after the multitasking release.
> 
> Regards,
>    Rob Craig
>    Rapid Deployment Software
>    <a href="http://www.RapidEuphoria.com">http://www.RapidEuphoria.com</a>

Okay, thanks. I don't think it is as important as the stuff you're working on.
Just inconsistent/unexpected.

Aren't ex.exe, exw.exe, and exwc.exe all compiled with Watcom?

--
"Any programming problem can be solved by adding a level of indirection."
--anonymous
"Any performance problem can be solved by removing a level of indirection."
--M. Haertel
j.

3. Re: Euphoria ctrl-c bug? [Reposted]

• Posted by ghaberek (admin) 1 month ago
• 1509 views

The phrase "at compile time" typically means "while the application is being compiled" Are you having trouble using Ctrl+C while the translator and gcc are doing their work? Or are you having trouble with allow_break() not working in your translated executable?

-Greg

P.S. Please refrain from reviving decades-old threads. It's best to start a new topic and link back to the old discussion. Once we get migrated to Discourse (still working on that BTW) ancient threads will lock automatically.

5. Re: Euphoria ctrl-c bug? [Reposted]

• Posted by ghaberek (admin) 1 month ago
• 1459 views

Interesting. I just did some testing and that appears to be the case. I will look into it.

-Greg