I am trying hard to think of a situation where unit prefixes are not
enough, but its hard to see.
2012/8/21 Timothy Madden :
> On 08/21/2012 02:17 PM, DaWorm wrote:
>> Very tedious, but you could create a wrapper unit and/or class for each
>> library, and expose a prefixed name instead of the orig
"With no error messages, or even with no changes to the program since 1
and a half year in the repository, the scientific calculations are now
all blown up, and program outputs only errors at runtime. The maintainer
now curses and chases me for having the nerve to leave a program
known as working i
In our previous episode, Timothy Madden said:
> Very ingeniuos, I believe this is as close to a solution as I can get
> for now.
>
> But there are still a few probles I can see:
>- there is no way to "prefix" symbols within a unit, that I know of.
Some languages related to pascal and maybe ev
Am 21.08.2012 14:10, schrieb Jorge Aldo G. de F. Junior:
"With no error messages, or even with no changes to the program since 1
and a half year in the repository, the scientific calculations are now
all blown up, and program outputs only errors at runtime. The maintainer
now curses and chases me
I already know that you can fully qualify, i believe you misread my post.
Its not that common to have name colisions if you use prefixes like i said.
I cant see how the added complexity of full name space support would
help pascal in that regard.
2012/8/21 Sven Barth :
> Am 21.08.2012 14:10, sch
Am 21.08.2012 15:13, schrieb Jorge Aldo G. de F. Junior:
I already know that you can fully qualify, i believe you misread my post.
Its not that common to have name colisions if you use prefixes like i said.
I cant see how the added complexity of full name space support would
help pascal in that
On Tue, Aug 21, 2012 at 1:29 PM, Timothy Madden wrote:
> On 08/21/2012 06:06 PM, Marcos Douglas wrote:
>> On Mon, Aug 20, 2012 at 1:15 PM, Timothy Madden
>> wrote:
> [...]
>>> Is there any form of proposal or some alternative to the USES clause,
>>> that will keep all the imported symbol names q
On Tue, Aug 21, 2012 at 1:43 PM, Timothy Madden wrote:
> On 08/21/2012 03:10 PM, Jorge Aldo G. de F. Junior wrote:
>> "With no error messages, or even with no changes to the program since 1
>> and a half year in the repository, the scientific calculations are now
>> all blown up, and program outpu
Timothy Madden wrote:
But next year, some unit I use will have reached a new version, and if I
merely recompile my program I have already have a conflict, that was not
there last year.
I'd suggest that the first thing to do is to document in each unit what
version of the compiler it's tested
On Tue, Aug 21, 2012 at 10:23 PM, leledumbo wrote:
>> Requiring all functions to be allways fully qualified will make the
> most commom case worse than current implementation just to be better
> for the uncommon case. This is a step back, not forward...
>
> Indeed, and the way unit system works ha
"Yes, we know too... but how prevent this using third-party libs?
For example, what do you think if I have a project that have a file
called lnet.pas? Can I use this identifier? I think so... WAIT, I
can't because the lnet project already uses, right? But I didn't know
before...ohh my... and now, I
On Tue, Aug 21, 2012 at 11:13 PM, Jorge Aldo G. de F. Junior
wrote:
> "Yes, we know too... but how prevent this using third-party libs?
> For example, what do you think if I have a project that have a file
> called lnet.pas? Can I use this identifier? I think so... WAIT, I
> can't because the lnet
Edit myunit.pas
Unit myunit.pas; <- backspace backspace backspace
Unit mynewunit.pas;
Alt-S Alt-X
Ren myunit.pas mynewunit.pas
No collisions now !
2012/8/21 Marcos Douglas :
> On Tue, Aug 21, 2012 at 11:13 PM, Jorge Aldo G. de F. Junior
> wrote:
>> "Yes, we know too... but how prevent this u
On Tue, Aug 21, 2012 at 11:34 PM, Jorge Aldo G. de F. Junior
wrote:
> Edit myunit.pas
>
> Unit myunit.pas; <- backspace backspace backspace
>
> Unit mynewunit.pas;
>
> Alt-S Alt-X
>
> Ren myunit.pas mynewunit.pas
>
> No collisions now !
Are you kidding me?
Third-party means: you can't change (can
Am 2012-08-22 13:45, schrieb Lukasz Sokol:
> Recompilation when one of units/libraries was upgraded, almost always implies
> rebuild. Who on Earth is so trigger-happy to upgrade, rebuild and not test for
> regressions? This is the only sane way to get the process going - document it
> *as MML said
Jürgen Hestermann wrote on Wed, 22 Aug 2012:
Am 2012-08-22 13:45, schrieb Lukasz Sokol:
Recompilation when one of units/libraries was upgraded, almost
always implies
rebuild. Who on Earth is so trigger-happy to upgrade, rebuild and
not test for
regressions? This is the only sane way to get the
Am 22.08.2012 12:37, schrieb Timothy Madden:
On 08/22/2012 09:57 AM, Marco van de Voort wrote:
In our previous episode, Marcos Douglas said:
[...]
Requiring all functions to be allways fully qualified will make the
most commom case worse than current implementation just to be better
for the
On Wed, Aug 22, 2012 at 9:22 AM, Jonas Maebe wrote:
>
> Jürgen Hestermann wrote on Wed, 22 Aug 2012:
>
>
>> Am 2012-08-22 13:45, schrieb Lukasz Sokol:
>>>
>>> Recompilation when one of units/libraries was upgraded, almost always
>>> implies
>>> rebuild. Who on Earth is so trigger-happy to upgrade,
On Wed, Aug 22, 2012 at 11:05 AM, Sven Barth
wrote:
> Am 22.08.2012 12:37, schrieb Timothy Madden:
>
>> On 08/22/2012 09:57 AM, Marco van de Voort wrote:
>>>
>>> In our previous episode, Marcos Douglas said:
>>
>> [...]
>>>
>>>
> Requiring all functions to be allways fully qualified will make
19 matches
Mail list logo
